New answers tagged

0

Ah, the bane of every tester. I should first remind you that you should control every factor to make them repeatable - which is a lot of effort. There's the environment (OS's, machines, connections/interfaces between them, then the application under test). Test fixtures are vitally important - setting the whole environment to a fixture in this case. But ...


1

If your application doesn't provide an interface for object based UI automation (such as MS UIA), which seems that's the case for you, and if you can't follow Andy's very correct suggestion; then you should look for an image processing based tool. Sikuli is the first that comes to mind, being open source and very successful (and probably being used by some ...


0

On HP ALM 11 Go to Test Lab, select the folder that you want to generate graph for. At your right you will see a pane with Live Analysis hyperlink. Click on that which will open up a small window with various filter options. Select on X axis the field that has your tester details e.g. responsible tester or test designer, etc. On Y axis choose your required ...


0

As a sole tester I can offer you some suggestions here. You may already be on this path. You have your manual standard path through the process: have you documented this? If not, document it first. Tribal knowledge can disappear very quickly when the one person who really understands the thing leaves. It doesn't matter how you document at this point. Next,...


0

Once test packs are created the main objectives of review and signoff process is to confirm test coverage and then categorise each and every test case into High, Medium and Low categories based on BI (Business Impact) and Likelihood of Failure. At the end of the review process you will have the entire test pack categorised. This approach helps to Identify a ...



Top 50 recent answers are included