| Sometimes during interview or simply your junior or colleague ask some kinda difference and you couldnt explain it properly cause incomplete knowledge. From this page you will find important differences in testing fields and automation testing. |
| |
| 1. |
Priority and Severity |
|
Defect Severity signifies degree of impact the defect has on the development or operation of a component application being tested. It is the extent to which the defect can affect the software. The severity type is defined by the Software Tester based on the written test cases and functionality. Defect Severity are of Critical, Major, Medium, Low (4 Types).
Defect priority signifies the level of urgency of fixing the bug. In other words Priority means how fast/ how soon it has to be fixed. Though priority may be initially set by the Software Tester, it is usually finalized by the Project/Product Manager. Defect Priority are of Urgent, High, Medium, Low (4 Types).
So priority is associated with Scheduling and Severity is associated with Standards/Functionality.
|
| |
| 2. |
Update Run Mode and Maintenance Run mode |
|
Update Run mode updates all properties of objects and checkpoints in case of failures. So if a object gets recognized using SMart identification then correct properties are updated in the OR. In case expected and actual values of checkpoints are different then they are updated as per the actuals.
Maintenance run mode is used when you want to update objects which are failing during execution. So if the object cannot be recognized at all with current settings instead of giving an error QTP will give a dialog to point the object to a new object if required.
|
| |
| 3. |
Monkey and Gorilla Testing |
|
Gorilla Testing, 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.
Monkey Testing is a software testing technique in which the testing is performed on the system under test randomly. The Input data that is used to test also generated randomly and keyed into the system. So as the scenarios that are tested are adhoc, system might be under stress so that we can also check for the server responses.
|
| |
| 4. |
StepInto, StepOver and StepOut |
|
These basically used when we debug any code but to understand these Steps, We need to take a scenario. Suppose we have two function A, B. We are debugging A function. In function A we are calling function B. so StepInto will execute all steps one by one.so you can see complete execution of function B. but StepOver will take complete B function as a unit and run complete function at once. And suppose using StepInto you entered in Function B, That’s the time we can use StepOut to come out from that function(like Step Over).
|