Hello.
We've recently started using Test Studio Ultimate, and so far the automatic testing seems fairly straight forward. We now want to create some automatic/hybrid tests that our manual testers can use while still "skipping the boring part" (logging etc).
Creating such a test is pretty simple: New manual test -> manual test steps -> select fast forward feature -> record the part you want the testers to be able to skip. Fair enough. However, there are a few issues we're having trouble with:
- When creating a manual test, you can add notes, screenshots and so on. This is a feature we like. Sadly, clicking the fast forward feature takes us to the interface for automatic tests, and there doesn't seem to be a way to return to the interface for manual tests. Is there a way to do that? Ideally, we'd prefer a situation where our developers can create the tests, but the testers still use primarily the manual test interface, as they're not going to use the recording feature.
- Statistics, results and reports seem to be exclusively based on test lists. For example, no reports ever appear in the "Report" section of Test Studio when manual tests are run. How can these features be configured for manual tests? We'd like keep historic data and full test reports for both manual and automatic tests. The closest we've got so far is the "save and exit" feature in the manual test, which allows a file to be created and then loaded into Test Studio. I suspect this could get quite messy in time with thousands of test files lying around.
Have a nice weekend.
Regards,
Svenn
We've recently started using Test Studio Ultimate, and so far the automatic testing seems fairly straight forward. We now want to create some automatic/hybrid tests that our manual testers can use while still "skipping the boring part" (logging etc).
Creating such a test is pretty simple: New manual test -> manual test steps -> select fast forward feature -> record the part you want the testers to be able to skip. Fair enough. However, there are a few issues we're having trouble with:
- When creating a manual test, you can add notes, screenshots and so on. This is a feature we like. Sadly, clicking the fast forward feature takes us to the interface for automatic tests, and there doesn't seem to be a way to return to the interface for manual tests. Is there a way to do that? Ideally, we'd prefer a situation where our developers can create the tests, but the testers still use primarily the manual test interface, as they're not going to use the recording feature.
- Statistics, results and reports seem to be exclusively based on test lists. For example, no reports ever appear in the "Report" section of Test Studio when manual tests are run. How can these features be configured for manual tests? We'd like keep historic data and full test reports for both manual and automatic tests. The closest we've got so far is the "save and exit" feature in the manual test, which allows a file to be created and then loaded into Test Studio. I suspect this could get quite messy in time with thousands of test files lying around.
Have a nice weekend.
Regards,
Svenn
6 Answers, 1 is accepted
0
Azhar
Top achievements
Rank 1
Rank 1
answered on 28 Jan 2014, 10:19 AM
Perhaps this belongs in the Test Studio forums? Should it be moved?
Regards,
Svenn
Regards,
Svenn
0
Hi Svenn,
Sadly, clicking the fast forward feature takes us to the interface for automatic tests, and there doesn't seem to be a way to return to the interface for manual tests.
You are right, once you choose the option Fast Forward, you are basically converting the test from manual to automated and I agree that once you do this, you no longer have the ability to add these notes and screenshots, and you can revert this test back to manual.
Here is a feature request I logged from your suggestion, feel free to vote for and track the progress of this feature using the link.
Statistics, results and reports seem to be exclusively based on test lists.
The reason why we take into account only the results from test lists is because quick execution is usually used when you are creating the test and you just verify that the test is working. Once the test is created, you should use test lists for executing these tests on a regular basis.
We appreciate your feedback, which we rely on to improve our product.
Regards,
Velin Koychev
Telerik
Sadly, clicking the fast forward feature takes us to the interface for automatic tests, and there doesn't seem to be a way to return to the interface for manual tests.
You are right, once you choose the option Fast Forward, you are basically converting the test from manual to automated and I agree that once you do this, you no longer have the ability to add these notes and screenshots, and you can revert this test back to manual.
Here is a feature request I logged from your suggestion, feel free to vote for and track the progress of this feature using the link.
Statistics, results and reports seem to be exclusively based on test lists.
The reason why we take into account only the results from test lists is because quick execution is usually used when you are creating the test and you just verify that the test is working. Once the test is created, you should use test lists for executing these tests on a regular basis.
We appreciate your feedback, which we rely on to improve our product.
Regards,
Velin Koychev
Telerik
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings
0
Azhar
Top achievements
Rank 1
Rank 1
answered on 31 Jan 2014, 01:46 PM
[quote]
Here is a feature request I logged from your suggestion, feel free to vote for and track the progress of this feature using the link.
[/quote]
Thank you!
Statistics, results and reports seem to be exclusively based on test lists.
[quote]
The reason why we take into account only the results from test lists is because quick execution is usually used when you are creating the test and you just verify that the test is working. Once the test is created, you should use test lists for executing these tests on a regular basis.
[/quote]
True, which is what we do for automatic tests. However, our testers generally run the manual tests one by one (including the manual tests with certain automatic sections). Can manual tests even be included in the test lists? If so, what would the purpose be? The tester still has to run each test individually and pass each individual step.
Regards,
Svenn
Here is a feature request I logged from your suggestion, feel free to vote for and track the progress of this feature using the link.
[/quote]
Thank you!
Statistics, results and reports seem to be exclusively based on test lists.
[quote]
The reason why we take into account only the results from test lists is because quick execution is usually used when you are creating the test and you just verify that the test is working. Once the test is created, you should use test lists for executing these tests on a regular basis.
True, which is what we do for automatic tests. However, our testers generally run the manual tests one by one (including the manual tests with certain automatic sections). Can manual tests even be included in the test lists? If so, what would the purpose be? The tester still has to run each test individually and pass each individual step.
Regards,
Svenn
0
Hi Svenn,
Can manual tests even be included in the test lists?
Yes, they can be included in a test list. It's the same way as you create an automated test list, you only have to change the test list type (see the attached screenshot).
If so, what would the purpose be? The tester still has to run each test individually and pass each individual step.
The benefits are similar to the one that you have with the automated test lists (like syncing the test list results with the Scheduling server, grouping similar tests in one test list, you can see reports for their execution, etc. )
Of course, you also have the option after you execute one manual test, to save the results files manually, but you are right that might bring some confusion if you have thousands of test files.
Regards,
Velin Koychev
Telerik
Can manual tests even be included in the test lists?
Yes, they can be included in a test list. It's the same way as you create an automated test list, you only have to change the test list type (see the attached screenshot).
If so, what would the purpose be? The tester still has to run each test individually and pass each individual step.
The benefits are similar to the one that you have with the automated test lists (like syncing the test list results with the Scheduling server, grouping similar tests in one test list, you can see reports for their execution, etc. )
Of course, you also have the option after you execute one manual test, to save the results files manually, but you are right that might bring some confusion if you have thousands of test files.
Regards,
Velin Koychev
Telerik
0
Azhar
Top achievements
Rank 1
Rank 1
answered on 05 Feb 2014, 01:54 PM
Indeed, I think such lists should suit our needs. We'll just have to be a bit creative when we make the lists. Thank you!
Regards,
Svenn
Regards,
Svenn