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

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.

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

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.

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.