As we all know that because of Agile Process we have frequent releases of products with new features. Thanks to Agile.
In order to cope up with these QA will face so many challenges in Agile Process.
Among all choosing right automation tool is also one of them .
Let us now see how Telerik Test Studio fits in Agile Process and fastens the QA work.
1. Source Code Management -
As we all know all the QA automation suites or artifacts should be maintained/controlled in some system. So if the automation tool is integrated with Source Code Management, it helps QA to check-in there scripts from the tool itself. This helps in avoiding using third party tools to check-in or check-out code to source control system.
They can get to know which files are out of sync with source control.
Telerik Test Studio supports TFS(Team Foundation Server) a Microsoft Tool, which provide source code management. QA team can work on Same Test Project allowing them to check-in at same time and independently.
TFS also helps collaboration between Dev and QA.
2. Bug Tracking System - I say most of the QA likes this tool :).
Most QA goal is to find the value bugs and log them in bug tracking tool. So to log an issue QA should write description, capture the screen shots, exception details, network log, dom tree etc.
Just imagine how happy tester will be if these are captured by automation tool :) Yes, Telerik Test Studio does it.
It will capture the screen shot as well as DOM structure automatically for failure cases.
Once your Test Studio is integrated with Bug tracking System, you can log bugs in Single Mouse click by just clicking on failure step and select 'Submit Bug' button. Tool automatically populates Bug Name and description and also we can it provides option for attach Failure Details to bug. These Failure details include Screenshot, logs and Dom structure.
Telerik Test Studio supports integration with Team Pulse Server, Team Foundation Server as well as Jira Server.
3. Integrating with IDE.
If the automation Tool has capability of integrating with IDE, tester can enhance the functionalities if there are any additional requirements for their automation.
Telerik Test Studio supports plug ins that can be integrated with Visual Studio.
4. Build Server Integration
This is also an important factor because in most of the companies there is a need to run automation scripts whenever new build triggers. So it will be better if we have this support in automation tool.
Telerik Test Studio supports integration with below Build Servers
1. TeamCity Builds
2. TFS
3. CruiseControl .Net Builds
4. Jenkins CI
5. Scheduling Test
Once the automation suites are ready to run it will be easy to testers if we have scheduling capability.
Telerik Test Studio offers this in Runtime Edition which involves Scheduling Server as well as Execution Server.
Apart from above Telerik also supports
7. Grouping of test cases by just adding a custom property to Test and we can run tests based on this property.
8. Generates results in 3 formats, excel, word and .aiiresult(Telerik Specific which gives complete logs and screenshots)
Detailed steps on how to integrate above tools with Telerik Test Studio can be found in Telerik Test Studio Documentation
In order to cope up with these QA will face so many challenges in Agile Process.
Among all choosing right automation tool is also one of them .
Let us now see how Telerik Test Studio fits in Agile Process and fastens the QA work.
1. Source Code Management -
As we all know all the QA automation suites or artifacts should be maintained/controlled in some system. So if the automation tool is integrated with Source Code Management, it helps QA to check-in there scripts from the tool itself. This helps in avoiding using third party tools to check-in or check-out code to source control system.
They can get to know which files are out of sync with source control.
Telerik Test Studio supports TFS(Team Foundation Server) a Microsoft Tool, which provide source code management. QA team can work on Same Test Project allowing them to check-in at same time and independently.
TFS also helps collaboration between Dev and QA.
2. Bug Tracking System - I say most of the QA likes this tool :).
Most QA goal is to find the value bugs and log them in bug tracking tool. So to log an issue QA should write description, capture the screen shots, exception details, network log, dom tree etc.
Just imagine how happy tester will be if these are captured by automation tool :) Yes, Telerik Test Studio does it.
It will capture the screen shot as well as DOM structure automatically for failure cases.
Once your Test Studio is integrated with Bug tracking System, you can log bugs in Single Mouse click by just clicking on failure step and select 'Submit Bug' button. Tool automatically populates Bug Name and description and also we can it provides option for attach Failure Details to bug. These Failure details include Screenshot, logs and Dom structure.
Telerik Test Studio supports integration with Team Pulse Server, Team Foundation Server as well as Jira Server.
3. Integrating with IDE.
If the automation Tool has capability of integrating with IDE, tester can enhance the functionalities if there are any additional requirements for their automation.
Telerik Test Studio supports plug ins that can be integrated with Visual Studio.
4. Build Server Integration
This is also an important factor because in most of the companies there is a need to run automation scripts whenever new build triggers. So it will be better if we have this support in automation tool.
Telerik Test Studio supports integration with below Build Servers
1. TeamCity Builds
2. TFS
3. CruiseControl .Net Builds
4. Jenkins CI
5. Scheduling Test
Once the automation suites are ready to run it will be easy to testers if we have scheduling capability.
Telerik Test Studio offers this in Runtime Edition which involves Scheduling Server as well as Execution Server.
Apart from above Telerik also supports
7. Grouping of test cases by just adding a custom property to Test and we can run tests based on this property.
8. Generates results in 3 formats, excel, word and .aiiresult(Telerik Specific which gives complete logs and screenshots)
Detailed steps on how to integrate above tools with Telerik Test Studio can be found in Telerik Test Studio Documentation
No comments:
Post a Comment