Monday 4 August 2014

Top Differences between Positive and Negative Testing



    Positive Testing (Valid)
   Negative Testing (Invalid)
1. Positive Testing means testing the application or system by giving valid data.
1. Negative Testing means testing the application or system by giving invalid data.
2. In this testing tester always check for only valid set of values.
2. In this testing tester always check for only invalid set of values.
3. Positive Testing is done by keeping positive point of view for example checking the mobile number field by giving numbers only like 9999999999.
or email like xyz@abc.com
3. Negative Testing is done by keeping negative point of view for example checking the mobile number field by giving numbers and alphabets like 99999abcde.
or email like 123sdhg#$%&^&.com
4. It is always done to verify the known set of Test Conditions.
4. It is always done to break the project and product with unknown set of Test Conditions.
5. This Testing checks how the product and project behave by providing valid set of data.
5. This Testing covers those scenarios for which the product is not designed and coded by providing invalid set of data.
6. Main aim means purpose of this Testing is to prove that the project and product works as per the requirements and specifications.
6. Main aim means purpose of this Testing is try to break the application or system by providing invalid set of data.
7. This type of Testing always tries to prove that a given product and project always meets the requirements and specifications of a client and customer.
7. Negative Testing is that in which tester attempts to prove that the given product and project does, which is not said in the client and customer requirements.

GUI Automation Tools

Following are some of the open source GUI automation tools in the market:

ProductLicensed UnderURL
AutoHotkeyGPLhttp://www.autohotkey.com/
SeleniumApachehttp://docs.seleniumhq.org/
SikuliMIThttp://sikuli.org
Robot FrameworkApachewww.robotframework.org
watirBSDhttp://www.watir.com/
Dojo ToolkitBSDhttp://dojotoolkit.org/

Following are some of the Commercial GUI automation tools in the market.

ProductVendorURL
AutoITAutoIThttp://www.autoitscript.com/site/autoit/
EggPlantTestPlantwww.testplant.com
QTPHphttp://www8.hp.com/us/en/software-solutions/
Rational Functional TesterIBMhttp://www-03.ibm.com/software/products/us/en/functional
InfragisticsInfragisticswww.infragistics.com
iMacrosiOpushttp://www.iopus.com/iMacros/
CodedUIMicrosofthttp://www.microsoft.com/visualstudio/
SikuliMicro Focus Internationalhttp://www.microfocus.com/

What is GUI Software Testing?

GUI testing is a testing technique in which the application's user interface is tested whether the application performs as expected with respect to user interface behaviour.
GUI Testing includes the application behaviour towards keyboard and mouse movements and how different GUI objects such as toolbars, buttons, menubars, dialog boxes, edit fields, lists, behavior to the user input.