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

[Feature Request] How about adding rerun failed test case function in the test framework? #963

Closed
lixuemin2016 opened this issue Apr 2, 2018 · 1 comment

Comments

@lixuemin2016
Copy link
Contributor

lixuemin2016 commented Apr 2, 2018

Hi Chirs,

Would you like to think about adding rerun failed test cases to lis-test framwork? Even we debug failed test cases continually, still cannot make sure all the test cases run pass 100% in Jenkins jobs.

Locally we run 110+ cases(subset of current lisa-test) on WS2016, 2012R2, 2012, Gen1, Gen2,x86_64 and i386(for rhel6 only) with same xml for every internal formal build. For the host WS2012R2 and 2012, we need to login the host to rerun failed cases, change the case xml file, also after pass, update the test result which is already uploaded to the test cases result manage system- Polarion. Generally it will spend time to rerun and re-update the test result.
After rerun, it will pass, e.g. timesync related test cases, although check the failure log and we can do some enhancement, if we already know what kind of cases can pass after rerun twice, it will great and it could save lots of effort.

We are planing to do re-run the failed cases locally, e.g. parse the cases.xml, select failed cases then rerun, merge test result by local script, but these work cannot be upstream and cannot benefit others. It will be so great if the test framework could support this feature.

Any suggestions for this feature request?

Thank you so much.

@lixuemin2016
Copy link
Contributor Author

Deal with rerun test case by script locally, no need to request lis-test to update, thank you so much.

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

1 participant