The online community for software testing & quality assurance professionals
Calendar   Today's Topics

Lost Password?


Quality Engineering >> Estimation and Planning

Pages: 1

Reged: 04/24/11
Posts: 67
Attributes in Test Plan
      #696990 - 01/29/12 10:56 PM

Hi All,
What are Attribute in Test Plan.Can Anybody Please explain with Example???

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 07/29/11
Posts: 60
Re: Attributes in Test Plan [Re: msrsharma]
      #697348 - 02/02/12 12:40 AM

Please find below the attributes to be covered in a test plan:

1. Scope of testing - E.g. how many screens to test

2. Related Documents - What all documents are needed to the QA engineer E.g. Functional Requirement, BRD, Design and mockups

3. Resource requirement (both s/w and h/w) - Machine configuration, Any automated tool to perform testing, Browser detail
application to test on etc

4. Staffing - How many QA resources

5. Test Environment - E.g. URL to access application, database server name, database name and connectivity details etc

6. Features to be tested - E.g. Functional testing which includes navigation, look & feel, driving etc. Data verification,
security testing, performance testing etc

7. Features not to be tested - Here you can mention if any particular feature or screen is not in scope of testing. Also it is
good to mention that 'Any thing which is not covered in Features to be tested section'

8. Assumptions/Preconditions - E.g. Requirements are frozen, Database will be ready with actual data loaded etc

9. Output - Data will be displayed on the UI or All mentioned functionality in the requirement will be implemented etc

10. Process to follow - Add all steps of QA process like understanding requirement, preparing test plan, strategy, test cases
etc till the sign off from QA step

11. Issue tracking system details - URL details of issue tracking system along with all steps to be mentioned in a bug to
reproduce it

12. Test deliverable - E.g. Test results in test case document, Bug summary etc

13. Dependencies and risks - E.g. delayed builds to QA, frequent changes to the requirements etc

14. Release Criteria - E.g. All issues are either resolved fixed or deferred, no P1 bugs etc

15. Pass/Fail Criteria - Pass criteria When actual result match with expected result. Fail criteria When actual result does not match with expected result

16. Exit Criteria - E.g. When there is large number of high priority bugs

17. Test Status Reporting - E.g. on daily basis status on % of test cases passed/failed/remaining etc

18. Test Schedule - High level schedule not detail here E.g. - 1st iteration of testing along with the start and end date, end to end testing along with start and end date etc

Please get back to me in case more details are required on the same or if you have some suggestion on the same


Post Extras: Print Post   Remind Me!   Notify Moderator  
Junior Member

Reged: 06/15/05
Posts: 13
Loc: NC, USA
Re: Attributes in Test Plan [Re: mbalajiwale]
      #697474 - 02/02/12 02:46 PM

Well said Balaji.

You can add couple more points as in

1. Roles and Responsibilities
2. Test Data
3. Estimation

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 07/29/11
Posts: 60
Re: Attributes in Test Plan [Re: Sathish.V]
      #697493 - 02/02/12 10:42 PM

Well roles are responsibilities are covered in Staffing...although yes I did put that as example there.
By Estimation do you mean we should add detailed estimation by breaking down the task to lowest level? If yes then as per my understanding estimations can be documented separately at that level and in test plan we can add high level estimates under schedule section. This will include the milestones to achieve and their start and end dates.
Test data yes, point noted we can add. Could you please provide more details on this particular point?

Post Extras: Print Post   Remind Me!   Notify Moderator  
Advanced Member

Reged: 05/11/05
Posts: 442
Loc: Pune
Re: Attributes in Test Plan [Re: mbalajiwale]
      #697512 - 02/03/12 01:52 AM

I think roles and responsibilities is important, more so in context of 3rd party testing. This section should define who will be doing what e.g. who will be creating/providing test-data, setting up the test environment

Another important section is assumptions.

I'd always like to add entry (when to begin testing) and exit(when to stop testing). Even suspension and resumption criteria is a real value add.

Post Extras: Print Post   Remind Me!   Notify Moderator  
Super Member

Reged: 09/15/10
Posts: 1887
Re: Attributes in Test Plan [Re: Juleo_2607]
      #697689 - 02/06/12 08:57 AM

You can also add Entry, Suspension & Redemption Criteria

<< Why are you so obsessed at finding bugs >>

Post Extras: Print Post   Remind Me!   Notify Moderator  
Junior Member

Reged: 01/04/05
Posts: 84
Loc: India
Re: Attributes in Test Plan [Re: MilesToGoBeforeISleep]
      #706963 - 05/15/12 03:42 AM


I feel at the top your section following section should be mentioned.

Introduction - Description about Project and Test plan.
Indented Audience Mention the details about stakeholders for which document is crated


Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 07/29/11
Posts: 60
Re: Attributes in Test Plan [Re: SACHIN007]
      #708728 - 06/04/12 04:10 AM

yes agree


Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1

Extra information
0 registered and 6 anonymous users are browsing this forum.

Moderator:  swt88, AJ, corklad, blueinatl 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Topic views: 10012

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5