Whats the meaning of features to be tested and features not
to be tested in Test plan?
Answers were Sorted based on User's Feedback
Answer / babji
in test plan
features to be tested : features means modules.what are the
responsible modules of the build for complete testing.
features not to be tested:
generally test eng concentrates on all the module's
functionality of the project.but in a few cases like
enhancement projects or the project with third party
involvement,in this cases testing team concentrates on only
required functionality but not on all module's functionality.
| Is This Answer Correct ? | 10 Yes | 1 No |
Answer / swathi
Features to be tested:
the list of all the features that are with in the scope and planned for testing will be listed out.
Features not to be tested:
the list of all the features that are not planned for testing will be listed out.
Ex:
1)out of scope features.
2)low risk features.
3)future functionality.
| Is This Answer Correct ? | 9 Yes | 2 No |
Answer / surya
Actually it was given in test plan where the test lead
decides what are the feautures to be tested in the
application and what type of testing to be done for example
in the given project there are two module where you were
asked to test particular module which u have to test which
is called features to be tested and the remaining are
features not to be tested thank u as per my knowledge
| Is This Answer Correct ? | 3 Yes | 2 No |
In an interview, what r the general questions asked in manual?pls give me anwser to this question?
what is tracebility matrix?
what is the criteria for selecting automation testing ?
hi am new to testing please anyone suggest a text book or materails so that it will help me to understand testing.please give me as soon as possible
can any one send sample test cases for database testing by taking an example? also leave emailid please. thanks (very urgent)
can any one give the example for high severity high priority high severity low priority low severity high priority low severity low priority
Can you explain calibration?
How you can decide the number of testcases are enough for testing the given module?
what r the topics coverd in maual testing? OR syllabus for manual testing
what is thetesting methodology that u r company folowing??
a project has to be released in one day but the testing people got that project from the developers half of the day before so what they have to do to complete the testing process.?
What do you understand by usability testing?