Using Quality Center to report on test runs works fine if you have a low number of tests or a test case to QTP test ratio of 1:1. However, if you are running multiple test iterations which all represent different test cases, then using Quality Center to keep track of test results is very difficult. Unfortunately, QTP does not yet have a built in method to let you determine the execution status of each iteration, nor does it provide a solution suitable for enterprise level automation reporting.
The purpose of this tool is to show you how you can use excel to design a report and pull out all of the information you need to determine the test result of each iteration and report this on a scalable level.
For the benefits of releasing something to the community, this is a very simple example. But it is possible to develop this idea further into a fully fledged Excel report that you can execute after each test iteration run, which will analyse multiple results in a very short space of time. (I currently have a version of this analysing 150 scenarios across 9 different language websites, so in excess of 1350 individual iteration results). The great thing about this is that it sits alongside Quality Center without any customisation that you need to put into your QTP code.
More information is included on the spreadsheet itself - so please go ahead and give it a try using the link below:
QTP Reporting Tool - Iteration Results Viewer
Monday, 7 February 2011
Wednesday, 2 February 2011
Resolved: QC Error: The server process could not be started because the configured identity is incorrect. Check the username and password
If you're trying to launch QTP tests onto a Windows Server machine, you may receive the following error "The server process could not be started because the configured identity is incorrect. Check the username and password".
This is because QTP needs to run in session 0 within the Windows Server, which has the administrative permissions required to launch your QTP tests. If you remote desktop into the server you can see your session ID by bringing up task manager (ctrl + alt + del) and clicking on the "users" tab.
If there is not a session 0 to connect to, then you can create one using the following command from the Start > Run menu:
mstsc /v:<servername> /admin
Just replace <servername> with the name of your server e.g:
mstsc /v:server1 /admin
This is because QTP needs to run in session 0 within the Windows Server, which has the administrative permissions required to launch your QTP tests. If you remote desktop into the server you can see your session ID by bringing up task manager (ctrl + alt + del) and clicking on the "users" tab.
If there is not a session 0 to connect to, then you can create one using the following command from the Start > Run menu:
mstsc /v:<servername> /admin
Just replace <servername> with the name of your server e.g:
mstsc /v:server1 /admin
Subscribe to:
Posts (Atom)