'MANUAL' test step type
Hello, We have some QA teams who have to do some manual testing and would like to use soapUI for verification of manual actions. The typical scenario for embedded teams and web teams is something lik...
Forum Discussion
Hi Ole,
Had some conversation with some other teams and received some very good feedback about this test step.
We have a web application teams and for them the biggest problem is website automation because during development the interface keep on changing so it is almost impossible to automate using any tool (selenium, qtp, watir). This team develops automation framework using selenium after code freeze. However, through out development they have to either do a lot of manual testing using excel sheets, SQL queries, REST/SOAP calls etc or write C#/Selenium code hoping that the UI does not change too much. So in short these guys think its a good idea too.
One very useful requirement came out of this discussion from a few teams. This step should contain an optional file attachment feature. So if you are running a testcase, and a manual test step fails, we typically capture screenshots (for websites), or take pictures (for cell phones etc). Most of the time we dump the screenshot in some network share so that they have linked via bug reports. In this case the junit report would have hyperlink to the location.
example Requirement:
Add attachment file: file share, network share location, url
Specify some comment: installing network driver causes windows vista to blue screen (see screenshot)
Ali
Had some conversation with some other teams and received some very good feedback about this test step.
We have a web application teams and for them the biggest problem is website automation because during development the interface keep on changing so it is almost impossible to automate using any tool (selenium, qtp, watir). This team develops automation framework using selenium after code freeze. However, through out development they have to either do a lot of manual testing using excel sheets, SQL queries, REST/SOAP calls etc or write C#/Selenium code hoping that the UI does not change too much. So in short these guys think its a good idea too.
One very useful requirement came out of this discussion from a few teams. This step should contain an optional file attachment feature. So if you are running a testcase, and a manual test step fails, we typically capture screenshots (for websites), or take pictures (for cell phones etc). Most of the time we dump the screenshot in some network share so that they have linked via bug reports. In this case the junit report would have hyperlink to the location.
example Requirement:
Add attachment file: file share, network share location, url
Specify some comment: installing network driver causes windows vista to blue screen (see screenshot)
Ali