Answer / rathnapriya

If we have to test the application in short period of time
we have to use risk based assumptions like,

*identifying the major functionalities and get it tested
first.
*Identify the risky modules
*Identify the functionality which is easily visible to
customers.
*Identify the functionality which has high financial and
safety impact on customers.
*Discuss with developers abt which part of the module is
developed under pressure that has probablity of error.
*Identify what type of testing cover multiple
functionalities.

Answer / kuldeep kr. pankaj

for this scenario we have to focus our testing on the major
functionality of the application to be sure that it is not
breaking & ensure that it is working properly ; as three
weeks time is not suffice to test the application.

Answer / rajkumargholve

As three weeks is very less time to do any testing. Tester
should follow a risk based approch. Tester should first
test all critical functionalities, & make sure they work
properly. Then if time permits he should test less
important functionalities as well.

Answer / murali

three weeks is very less time to test an application. here
tester should use monkey testing or gorilla testing

Answer / saff

for any appln if time is the constraint we need to focus
only on the risk which are involved in that aplln and test
to mitigate those risk

testing types it depends on the type of the product or
project we are developing
if it the s/w where user are internal to customer
then there is no need to test apperance and performance
testing

but we need to check wheather it is of any use to customer
and reasonably bug free

andif it is a s/w where it is used by num of people then
the testing types should be like usablity ,system ,user
friendliness ,perfromance all this should focus on reducing
the risk involved


correct me if i am wrong
saff5005@yahoo.com

Answer / dbs

In this case we need to mainly concentrate on the mandatory
fields in the application where by clicking on 'save'
without entering the mandatory fields an error message with
the proper meaning should be displayed, then we need to
concentrate on the flow i.e.,about the user friendly.

This case mainly depends on the size of the application and
also depth of the application

Answer / thiyagarajan veluchamy

Hi,

Three weeks not enough to test the application. But we can
test the major functionality of the application(Smoke
Testing). If you know the complete features of the
application then follow the Ad-hoc method.

Thanks,
Thiyagarajan Veluchamy

what is the main difference between high and low level design in sdlc

11 Answers   Accenture, Infosys,

What is the difference between Smoke Test & Sanity Test?

10 Answers   Qualtree Solutions,

at which movement we will perform varification testing & Validation Testing , with Example ??

7 Answers   NIIT,

Testing process in your company?

1 Answers   OM IT Solutions, Oracle, TCS,

Do you use any automation tool for smoke testing?

0 Answers  

i finished writing test caes, logged bugs and also regression testing i finished.when we do user acceptance testing?

3 Answers  

Write the Test Cases for Ball Pen and Water Bottle.

14 Answers   Chetu India, Quexst,

How to write test scenario for white board?What is scenario? pls explain me with example.

2 Answers   CTS,

Description--->There are 5 modules in my application. On every module there is a date box. In 1st module, date box is used for 2 submenus. My Question is ---> Should I have to write test cases for date box for every modules & submenus?

2 Answers  

What r the checklist to review testcase?

7 Answers   AZTEC,

What is meant by YUI testing?

1 Answers  

What is defect clustering

3 Answers   Genpact,