You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
As of now, we are automating test cases without any reference to the test case ID. We are only using the feature tags and no other tag.
To handle the ambiguity, we can add the Test case ID as a decorator for the test cases.
This would help us actually sync the automation status with test rail as well as in future, it would be easy to review the test case status with test case ID in the report as well.
Yes, we are thinking of similar, however it will be a major task to integrate TestRail for now.
Currently, we were just planning to add Testcase Ids from Testrail to the feature scenarios like tags, so that once the execution result is available we can, mark the testcase manually for now as pass in automated test plans in testrail.
As of now, we are automating test cases without any reference to the test case ID. We are only using the feature tags and no other tag.
To handle the ambiguity, we can add the Test case ID as a decorator for the test cases.
This would help us actually sync the automation status with test rail as well as in future, it would be easy to review the test case status with test case ID in the report as well.
cc @pazone
The text was updated successfully, but these errors were encountered: