Given time is short and u have to test and release application,what approach u follow to test?

  • Interview Candidate
  • 32
  • 2940

Showing Answers 1 - 32 of 32 Answers

meena

  • Sep 10th, 2005
 

By considering requirements specifications which module is more important and complex first i test that one and if time permits i will do testing for remaining also.

  Was this answer useful?  Yes

raakesh reddy

  • Jul 6th, 2006
 

i will perform adhoc testing

  Was this answer useful?  Yes

TestSau

  • Jun 30th, 2007
 

1. We have to test the area which was not tested in previous build.
2. Need to test fixed bugs raised in previous build.
3. Perform basic verification test cases (BVT's).
4. Test area which was developed in a hurry.
5. Test the most used e2e scenario.
6.  Perform P1 S1 test case execution.

  Was this answer useful?  Yes

Anand

  • Nov 17th, 2007
 

We do ad hoc or exploratory testing.

If we are very near to our release then we do risk analysis based on the requirement Severity and priority

  Was this answer useful?  Yes

ramumcato

  • May 31st, 2008
 

1) Select the key areas on all modules, which are key to work the s/w smoothly and visualized by custemer, frequently usage modules by customer.
2) do the equivalance partitioning effectively
3) preapare test data effectively ( possible ways based on time we have )

then write the testcases and start testing.  finally if we have time we can do ad-hoc testing before doing system testing.

srinivasulub1981

  • May 23rd, 2009
 

First of all we need to verify below things and can test execute the concerned test cases...
Which functionality is most important to the project's intended purpose?
Which functionality is most visible to the user?
Which functionality has the largest safety impact?
Which functionality has the largest financial impact on users?
Which aspects of the application are most important to the customer?
Which aspects of the application can be tested early in the development cycle?
Which parts of the code are most complex and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
Which aspects of similar/related previous projects caused problems?
Which aspects of similar/related previous projects had large maintenance expenses?
Which parts of the requirements and design are unclear or poorly thought out?
What do the developers think are the highest-risk aspects of the application?

Chinmay S Tester

  • May 10th, 2010
 

I perform Sanity testing if I have enough time, otherwise we take random testing.
But in random testing we are not dealing with all basic features of software.
Hence from my point of view, Sanity testing is best option.

  Was this answer useful?  Yes

dadwalm

  • May 24th, 2010
 

I would suggest performing Risk Based testing. Identifying the requirements which if not implemented or wrongly implemented could result into a disaster, prioritize such requirements with the help of Business and resume testing.
If you have a UAT team, suggest them to start in parallel to help early detection of the defects.
Sanity testing will obviously have to carried out to provide you the confidence on the release.

  Was this answer useful?  Yes

mithr17

  • Nov 17th, 2011
 

Instead of creating test cases for each and every requirement, I would create test scenarios that cover multiple features and modules. This way I’m thinking in the feet of an end-user and finding risky and important (to the client bugs; covering tasks performed by end user; best use of time and budget allotted to testing; making sure core functionality is bug free; covers multiple test cases under one scenario.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions