Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Done
-
None
-
None
-
R3.4.0 S5, R3.4.0 S4
-
Description
The main reason for failing is due changes in the Jira-Target
Imagine a scenario where, in the Jira-Origin, there is an Manual Test Issue called A-1 with the following steps:
Step | Data | Expected Result |
---|---|---|
Step 1 | Step 1 | Step 1 |
Step 2 | Step 2 | Step 2 |
Then a backup file is generated, it will contain the info regarding the issue A-1, including its Steps.
After this, the project A is imported into the Jira-Target. Everything should be imported with success.
Then some time passes by, let's say a week. There could've been lots of activities under the issue A-1 in the Jira-Target. Let's imagine that during this time the step 'Step2' was removed.
Then the project B is imported, the process will fail with the following error:
unexpected error occurred while importing the project with key: XP
java.lang.NullPointerException
at com.xpandit.raven.imports.project.ao.TestStepImport.handleEntity(TestStepImport.java:103)
This happens due to the fact that the Step2 was removed from the issue A-1 in the Jira-Target but the backup file says A-1 has a Step2.
Note: May also happen when changing the issue type
Attachments
Issue Links
- mentioned in
-
Page Loading...