There is a new build and you have not much time left behind to test(manual test), what will you do? (apart from prioritizing functionalities..... risk analysis, what other answers are valid approaches to this interview question?
If you donot have much time to test the whole application, then the best approach is by giving priorities to the functions or the modules.
For example, login window of an application has a very high priority, caz it authenticates the user and allows the users to access the application.
Another example, if its a database apllication, you need to check the users rights in the login screen, data storing by checking data addition, deleting and edyting etc.
If you donot have much time to test the whole application then the best approach is by giving priorities to the functions or the modules.
For example login window of an application has a very high priority caz it authenticates the user and allows the users to access the application.
Another example if its a database apllication you need to check the users rights in the login screen data storing by checking data addition deleting and edyting etc.
As per the standard process we prepare the Post Live Scripts which are nothing but the very high priority test case. These are prepared during the Functional testing of regular builds. If some build/Changes comes up at eleventh hour then I feel is the best way- 1. Test around the impacted areas with new change 2. Followed by a quick regression using PLS.
According to me I will test atleast for evey page is loading or not.
Also we will check the basic purpose for actual the system is built. Suppose if we have built system for bidding purpose so will check if Applicant is able to Bid or not.
And also new check the functionality which will newly introduced or any other bugs fixes for that whole area (Its Imapct as well) If possible
Here i'm writting what we have done in my project is we can conduct Adhoc testing on the major functionalities based on our knowledfe with out test cases and test results. I feel it's the best way than all
From my point of view is ad hoch testing is more useful in this type of situation but we don't have the specification of the project then we should go for the explotary testing because we use explotary testing when we don't have the time and specification.
In addition to my previous post we can do the testing based on E2E test cases if prepared.. Now a days it's better to prepare the E2E test cases for every module.
When Major Release date is in the nearby then build release date will be decreased some times for every 2 days New build might be released its all depends on the fixing of Issues and based on their importance so having less time is a common scenario and at this point of time its obvious that we cannot execute all the test cases. In such situations apart from Prioritizing high critical functionalities and risk analysis we can go with the test cases or test scripts.
1) which are a part of Core test cases or scripts
2) Areas which are highly accessed by the end user
3) S1/2/3 bugs
4) Positive test cases
5) Functionalities/modules that are having more bugs and
If there is less time limit to test for First build with out using Priortize functionality Risk Management then --Check for the Sanity test first. --Check the application flow once in the Time limit --Make up over the important Functionalities and GUI check (All controls butons drop down list radio buttins text box) --Ensure that no Page cannot be found or Show stopper in the Application.
Lets do the brief testing on next builds to find more bugs and increase the quality for the application
1 
1