expected and actual result
This is a discussion on expected and actual result within the Software Testing forums, part of the Archive category; [FONT="Century Gothic"][/FONT] hi Whenever u select GUI OBJ/WIN checkpoint it captures the whatever present in the application as expected and ...
how WR recognizes expected results?
Whenever u select GUI OBJ/WIN checkpoint it captures the whatever present in the application as expected and as well as actual.
suppose the cusomer gave the requirement as the Student Name in the application should be "Mythri".
But while developing the application by mistake development team put it as "Mythi".
the same application came to testing team ,they had customer requirements with them.
Then they put GUI Checkpoint for Object/Window and they captures the name in the application.ie.Mythi.
There it will give an option as Expected Value:Then the testing team provides "Mythri"which is exact expected value of customer.If run the test the test fails.Then the testing team will send a defect report to development team mentioning that.
Yes whatever is the current state when you record a test is the expected and then when you run it again it may be after a day or after a month whatever is the scene at that time it will compare the actaul result that it gets at that time with the results that you have stored while recording.
Thus exepected result is the reslt when you are recording.
Actual is the result that ou are getting when you run the test.
If not then then something is broken after you recorded and hence it is a fail.