Dear,
We are currently trying to find a way to improve the testing column. The problem that we are facing now is. Sometimes the developers put it into the testing column but it's not yet testable or needs to be tested by the test engineer. I wanted to know how we can improve or identify in a better way, such as the test engineer knows. Now I can start testing. Please help us out with this.
One suggestion to improve the bug reporting experience is to check in with development teams often to ask if they need any more information. Another suggestion is to encourage customers to report each problem on a separate request to help track bugs. As for identifying when a task is ready for testing, it may be helpful to have clear criteria or guidelines for when a task is considered testable and ready for the test engineer to begin testing.
Hi @yasin.donmez ,
You could add another state in your workflow just before testing so when developers finish development they can move the ticket there and it will be assigned to test engineers and once it is done, then the test engineers can move it to testing column.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @yasin.donmez , as @Najm Polaris has suggested, you may want to add another column to your board. One idea is to have a column where the developers put the tickets they *think* are ready for testing. Then, the test team can validate that they really are ready for testing and move them to the testing column, or move them back to development if they're not ready yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks everyone!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.