Hot answers tagged

6

As of my reading- Guerrilla Testing means going into a coffee shop or another public place to ask people there about your product or prototype. It can be conducted anywhere ex- cafe, library, train station etc, essentially anywhere where there is significant footfall. Guerrilla testing works well to quickly validate how effective a design is on its intended ...


4

What is Guerrilla Testing : it is a way to get some quick user feedback on your product or prototype. I can say its usability testing. Guerrilla Testing Covers : it covers an activity by which you need to conduct it where your audience are novice users and observe these - Can they find the content? Is the language relevant to them? Have they understood ...


4

What you are asking for is a fault injection. Unfortunatelly, you are not enough specific in what kind of error you want to reach and there is a lot of different states from bad blocks causing read-write errors to no rights or disconnected devices during the process, etc. This answer on another project will make you happy under Linux: ...


2

Gorilla Testing is a testing technique in which testers or developers also join to testers to test a particular module thoroughly in all aspects. Gorilla Testing is a technique in which repetitive Manual Testing process, which a tester would have done several times before, is done again to test the robustness of the system. Here, one module of the ...


2

Guerilla testing is an inexpensive but highly effective form of test in which a product is subject to high levels of stress until failure. You can see a classic example here.


2

Telerik's Test Studio is also a good tool and will provide you required support and features. You can use this tool for testing Web, Mobile, Desktop (but only WPF) applications. test Complete is also a good tool which will suffice your requirements (advantage is it supports more variety of Desktop applications). Again, cost wise Test Studio is cheaper than ...


1

As your building Windows desktop applications have you looked at what MS has to offer? I think their Lab Management tools are designed for these challenges. Combined with TFS build server its should be able to bootstrap an test environments on the fly for each build and test run. And here an article about combining TFS, Lab Management and CodedUI: ...


1

I've handled this before by killing the process with driver.quit(); and then re-initializing the driver and getting the URL. That will definitely kill the session, because it's running in a new JVM. Since it's the same test, you can still pass strings and integers to the new driver. Simplified Example: driver.quit(); driver = new firefoxdriver(); ...



Only top voted, non community-wiki answers of a minimum length are eligible