Common - What happens to the test plan if the application has a functionality not mentioned in the requiremen

GeekInterview.com > Interview Questions > Testing > Common

Go To First | Previous Question | Next Question

Common | Question 188 of 249

What happens to the test plan if the application has a functionality not mentioned in the requirements?

Total Answers and Comments: 8

Last Update: November 14, 2009 Asked by: sushkumar

Sponsored Links

Best Rated Answer

—

Submitted by: vk1978

The availability of functionality in the application that is not mentioned in the requirements, first such things will be raised in the team meetings and communicate the same with development team and also will raise that issue as a defect whether that functionality is impacting on regular functionality or not.

Above answer was rated as good by the following members:
hasini15

June 27, 2007 03:21:56

Vishwa Ranjan

RE: What happens to the test plan if the application h...

I belive it should be consider as a BUG because any thing which is not mentioned as requriement can be consider as BUG rather it is good or bad. We can suggest to add that functionality in the next built but before that we has to consider that as a BUG only.

I look forward to your feedback.

Thanks
Vishwa Ranjan

Is this answer useful? Yes | No

September 24, 2007 04:13:23

karunakaran.S

RE: What happens to the test plan if the application h...

Yes i am 100 sure that its a bug and not an issue also.
But i think there is nothing affects Test plan with effect to this bug.

Is this answer useful? Yes | No

November 23, 2007 01:46:46

sandeep kumar

RE: What happens to the test plan if the application h...

I Agree what they are saying but it depends on organisation have different rules
some small company dont provide document and they inform what this project consists in that condition you have to study the project and assume yourself this functionality should work like this. This Type of testing is called Adhoc testing without any plan and test cases

Is this answer useful? Yes | No

March 18, 2008 08:44:56

cjayesh123

Member Since: July 2006 Contribution: 1

RE: What happens to the test plan if the application has a functionality not mentioned in the requirements?

Everybody I respect your sentiments towards Testplan But it cannot be treated as a Bug or an Issue but it needs to be treated as a Change Request and this will be marked in the RTT (requirement traceability Metrics) as CR and will be released in next build or version if it is approved by Customer for additional cost if it is major functionality or approved by the delivery PM if it can be given free of cost as the case may be. Onthing more Testplan is a dynamic document which can be changed over a period of time by having change control mechanizm. Based on the same Test Schedule is prepared.

Is this answer useful? Yes | No

March 22, 2008 16:41:21

saransh.kanaujia

Member Since: February 2008 Contribution: 20

RE: What happens to the test plan if the application has a functionality not mentioned in the requirements?

A test plan is possible to write on the bases of srs. If srs is also not availble we have option to first test the project and then write test plan according to that. I thing it's a good practice to deal with project like this.

Is this answer useful? Yes | No

April 15, 2009 16:06:29

vk1978

Member Since: February 2009 Contribution: 174

RE: What happens to the test plan if the application has a functionality not mentioned in the requirements?

The availability of functionality in the application that is not mentioned in the requirements first such things will be raised in the team meetings and communicate the same with development team and also will raise that issue as a defect whether that functionality is impacting on regular functionality or not.

Is this answer useful? Yes | No

1 0

Overall Rating: +1

September 18, 2009 01:03:15

rahulskin

Member Since: November 2007 Contribution: 39

RE: What happens to the test plan if the application has a functionality not mentioned in the requirements?

It is Requirement Specification defect.
After updating the Requirement Specification the testing plan can be updated based on the change in the RS.

Is this answer useful? Yes | No

November 14, 2009 18:56:21

kurtz182

Member Since: November 2009 Contribution: 151

RE: What happens to the test plan if the application has a functionality not mentioned in the requirements?

When an application has functionality that is not covered in the requirements the Business Analyst (BA) needs to be notified and either the BA or Project Manager (PM) needs to submit a Change Request. Afterward this new functionality needs to be documented in the Business Requirements Documentation (BRD). Once this has occurred then the tester creates test cases based on the requirement(s) and maps the requirements to the test cases through the quality management tool (also known as a defect management tool). When the test cases are mapped to requirements this new functionality can be also called out in the project's Test Plan.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank