sam

• Nov 11th, 2005

 

With out a requirements documents how can u develop an application .

if it is developed without any requirements then the application is made with assumptions .Then testing is done depending on the assumptions made through application.

ctan

• Nov 12th, 2005

 

sam Wrote:

With out a requirements documents how can u develop an application .

if it is developed without any requirements then the application is made with assumptions .Then testing is done depending on the assumptions made through application.

In this case, if you are going to work for some company, and you are going to take a test on the application, but all the previous documents are gone without a trace. But you still have to do the testing. Yes it was a question that i faced. So I want to get some idea on that.

cathyhongzhao

 Profile Answers by cathyhongzhao 

• Nov 25th, 2005

 

I have been asked the same question, anybody has any idea about this?

suma_806

 Profile Answers by suma_806 Questions by suma_806

• Nov 29th, 2005

 

We can test the application with general assumptions if no requirement doc is available. We can test High severity issues like show stoppers, page crashes, unexpected behavior and etc.

If that is a web application we can go for,

Usability testing -- User Friendly ness of the system.

Reliability testing -- Whether Active buttons are really active, correct menu options are available, correct hyper links are available

Compatibility testing -- Testing the application with different sets of  Browser.

Functional testing (if any previous docs are available)

Performance testing.

Pls let me know, if I am wrong.

Regards,

Suma

 

 

juking

 Profile Answers by juking 

• Dec 1st, 2005

 

the best strategy to do this type of testing is exploratory Testing,learning the application as you test it and ensures that all functionalities are working in the intended way.

manjunath

• Jan 9th, 2006

 

we run all the old existing test cases and  check the application, these test cases we would   have prepared when preparing an application,

or  we will check the application according to the   user manual we have and then test  it according to it.

if any thing new is to be added  we test it based on information collected

Basivi Reddy

• Jan 20th, 2006

 

As I understand, the best way is

1. Have discussion with the customer and Developer

2. Understand the Core and cosmetic requirements

3. Document them roughly

Based on the document you prepared start testing to check

1. Consistency of GUI screens, buttons for look and feel

2. Check the correctness of the formulae and logics

3. Check for the correct navigation and integration

4. Check for the environments on which it has to work.

and offcourse some more.............

Manjula

• Jan 26th, 2006

 

If the application is given without providing the FRS, Do the adhoc testing then write the high level test cases { Sometimes also called the trace ability matrix without the reference numbers(FRS no,?s)}. After understanding the whole application then I will write the test scripts.

Manjula

• Jan 26th, 2006

 

If the application is given without providing the FRS, Do the adhoc testing then write the high level test cases { Sometimes also called the trace ability matrix without the reference numbers(FRS no,?s)}. After understanding the whole application then I will write the test scripts.

Ravi kumar

• Mar 15th, 2006

 

Hi,

If there is no requirements are available will test Adhoc testing.

Adhoc testing means the tester will test the application with his ideas.

meevikas

• Aug 14th, 2006

 

In some product based companys we didn't have client requirements.

In starting stage there will be no clients. In that case we have to test the application without requirements

  in this case we have to discuss with developement people who has developed the module.

he will explan the flow of module and we can perform testing.