Sr Testing engg/ Test Lead execute a set of selected testing
to verify whether development initial released is stable or
not. Simply to verify the stability of the build release to
further continue with testing with resting of testing team.
It is a type of testing in which one will conduct overall
testing on the realesed built weather to check the build is
proper or not for the detailed testing
to do so one need to see
1 whether the application is properly installed in the
environment or not.
2 whether all the functionality are there or not
3 whether one can navigate to all the pages or not
4 whether required connections are working fine or not..
Whenever we receive the build this is the first test conducted to the basic functionality of all the requirements. During the test run each requirement open the window performe basic functional testing. Then the test is conducted to verify the build is qualified for features derailed testing. The per pose of this test is if any cretecal defects are found we can report at earlier stage. This is also called sanity testing. After sanity test the status either pass or fails is reported to developer.
Whats'the difference between Seviroty and priority ..
Please answer in the follwoing way ?
1) Who will give the priority and Sevirity (ex -
client/users and testers/developers) ?
2) If the client wants to give a high importance to an
issue and for that the QA and developement don't think that
much importance then how would be the situation ?
3) If a high sevirity issue is there but another issues is
there with high priority .. Then which issue will be fixed
first and vice versa ?