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
The automatic tests from the Actions tab cover a lot of the use cases that need to be tested during new releases, yet some members of the QE team (me included) often choose to test everything manually, which wastes a lot of time compared to checking the results of the automatic tests cases and testing manually the remaining ones. There are some reasons for this:
There is not much information regarding what does each workflow actually do and in which case(s) they should be used
There is not much information on how to properly configure the parameters of the workflow executions in order to get the desired results
There is no clear correlation between the results that appear on the test reports of the workflows and the test cases from the QE testing results sheets, which makes it confusing to figure out which test cases are actually working or not
So, by adding a document of reference that includes enough information on the above topics, we can teach the team about the workflows, improve the performance, and streamline more the testing process.
Also, it would be really helpful to note in the QE testing results sheet which cases are actually covered by the workflows, but that may be out of the scope of this issue.
The text was updated successfully, but these errors were encountered:
The automatic tests from the Actions tab cover a lot of the use cases that need to be tested during new releases, yet some members of the QE team (me included) often choose to test everything manually, which wastes a lot of time compared to checking the results of the automatic tests cases and testing manually the remaining ones. There are some reasons for this:
So, by adding a document of reference that includes enough information on the above topics, we can teach the team about the workflows, improve the performance, and streamline more the testing process.
Also, it would be really helpful to note in the QE testing results sheet which cases are actually covered by the workflows, but that may be out of the scope of this issue.
The text was updated successfully, but these errors were encountered: