Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test has unexecuted status because of "WARN: Test XXXX not found in Test Cycle." #16

Open
chamElE0 opened this issue Oct 17, 2017 · 3 comments

Comments

@chamElE0
Copy link

build 17-Oct-2017 09:09:36 ##### INFO: Linking Test Cases to Test Cycle:[ENBD-1374, ENBD-1375, ENBD-1376, ........, ENBD-1577, ENBD-1578]

After that I got
build 17-Oct-2017 09:10:35 ##### INFO: Setting status PASSED for Test: ENBD-1577
build 17-Oct-2017 09:10:35 ##### WARN: Test ENBD-1577 not found in Test Cycle 1017_ENBD_ip:port/W4DEV32_feature-feature_17.7.tat-62
build 17-Oct-2017 09:10:35 ##### INFO: Setting status PASSED for Test: ENBD-1578
build 17-Oct-2017 09:10:35 ##### WARN: Test ENBD-1578 not found in Test Cycle 1017_ENBD_ip:port/W4DEV32_feature-feature_17.7.tat-62

And test still was marked as 'Unexecuted' in jira.

But in the log I see "INFO: Test Cycle is not in sync. Giving Zephyr another chance." another attempts of sync in such cases, but not at this time.

Why resync didn't happen always?

@arturitos
Copy link

As far as I understood all test cases were assigned to test cycle correctly, but some statuses were not updated. Please correct me if I misunderstood that.

Resync is called only during test linkage to cycle, in situation when amount of linked test cases in JIRA differs from amount of test cases passed to JIRA for linkage.

You can check the code here:
https://github.com/ctco/zephyr-sync/blob/b83e03534cb91cc5c7cf191719d5ae4e3bb2bc0d/zephyr-sync-core/src/main/java/lv/ctco/zephyr/service/ZephyrService.java

Could you please provide full log? Probably it could give a clue to your issue.

@chamElE0
Copy link
Author

As far as I understood all test cases were assigned to test cycle correctly, but some statuses were not updated. Please correct me if I misunderstood that.

Yes that's correct.

@chamElE0
Copy link
Author

I'll try a new version and back with results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants