If there is no sufficent time for testing & u have to
complete the testing then what will u do?
- 20 Answers
- 24992 Views
- Fidelity, HCL, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / pramod
When you has less time to do testing,you can do your
testing if you have all test case ready with you.Just
execute all test cases(Automated testing)you will get
results.
Specically for manual testing you should do smoke testing
to check all links.After which whichever module or
functionality you want to release check it as per the
requirement specification instead of going in detail
scenario,if it works the enough.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / vishwa
Risk based approach for testing sounds more meaningful in these situations. As its(Risks) the one which we test for. Identify the Risky areas from Buisness perspective, user perspective, application perspective.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / madhukar9823
If we doesn't have enough time for testing then it is
completely based on risk management factor, we have to
select the module which is having more priority, by based on
the priority for the module we have to finish our testing
process
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / chaitanya deshpande
Hi everyone,
All the above answer seems very correct. But,carrying out any kind of testing (Smoke, Sanity, Risk Base) wont be enough if we miss any crucial functionality.
Testing process has some steps and formal documentation like Test plan, test cases, Reviews of those documents.
So I think if time to complete the testing is less we can skip these formalities of test plan, reviews,approvals and all and directly jump on test case preparation and its execution.
Different approach can be taken while authoring and executing the test cases. It might be Smoke, Sanity or risk based.
Suggestions are welcome.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / aishwary mishra
If there is no sufficient time the we need to keep some
scenario while testing the application-
1-Check all the major functionality
2-Check all the functionality which is most visible to user
or user is going to use most frequently
3-make scenarios based upon business requirement and execute
them.
4-Do smoke testing
5-check UI properly
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / bizz
This is very know fact that Testing has always a time
constrain. But its always sufficient to complete before
time provided u work little harder. If in some situation
when time is really not enough to run all the Testcases
then we can execute Smoke Testing. Smoke testing the
execution of the basic testcases of the application.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / govind
At that time you can prefer Adhoc testing (Testing the
product of system without any documents)
| Is This Answer Correct ? | 0 Yes | 2 No |
Answer / rafi
at this situation we have to perform adhoc testing
| Is This Answer Correct ? | 0 Yes | 2 No |
how does a client server environment affect testing?
Hi, This is vkram.I had completed my B.E in May 2005 & currently i am undergoing Testing Course. I want to join as a Fresher in any MNC. What should I tell why u r coming to testing field & what u did this 2 years?
what all the metrics to be checked for a document ?
What is the difference between GUI and UI testing?
levels of testing
explain v model detaily plese
What is the smoke testing and sanity testing..?what is the difference?
what is a buglist?
what is user interface testing?
what is the way to explain about project of 3 years experianced
what is the difference b/w system testing & functional testing ?
What is Automation Test frame work ?
Automation Testing 
