Folder Structure Management
Download
Report
Transcript Folder Structure Management
Folder Structure
Management
Best Practice
By
Gabriel Rodriguez
Agenda
Folder Structure for Software Testers
Folder Structure for QA Managers and QA
Leads
Q&A
Reference
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software
Testers
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
The following folder structure is based on the testing life cycle
processes.
There are a lot of benefits in organizing your data using this
structure
– Files will be stored in a systematic way
– Files will be easy to find
– Historical data for future projects
– Work evidence of your tasks
This folder structure can be tailored to meet your needs. (Note:
This best practice is based on a real world scenario, ONYX is the
name of the project so make sure to customize this best practice
to your own project.
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
Folder structure example
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
Description of the folder structure:
– Nemesis Shared Folder
Every team member at Onyx must have a shared folder in
\\Nemesis\General\
– Onyx Project
The folder structure depicts several projects (i.e.,
Washpad, Dragnet, Stardust…) You can start creating
folders for each project you have participated
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
Description of the folder structure:
– Testing Life Cycle Folder Structure
This is the recommended structure to store all your historical
data, the structure is composed of the following testing life cycle
processes:
– (1) Risk Analysis
– (2) Planning Process
– (3) Test Design
– (4) Performing Test
– (5) Defect Tracking and Management
– (6) Quantitative Measurement
– (7) Test Reporting
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
Description of the folder structure:
– Additions to the folder structure
This is the recommended structure to store all your additions
during your daily activities, remember that you can always tailor
this section to meet your needs:
– (i) SDLC Documentation
– (ii) Peer Review Notes
– (iii) QA Meeting Notes
– (iv) Project Meeting Notes
– (v) Testing Literature
– (vi) Templates
– (..) …
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
This is a brief description of the type of data that you can store in each
folder:
– (1) Risk Analysis
Store Risk Matrix
Store any Risk document related to testing
The following documents can be stored if any risk analysis was
performed on them, otherwise store them in a separated folder
(Addition Structure)
– Requirement Documents
– Functional Documents
– Design Documents
– (2) Planning Process
Store Test Plans
Store QA Project Plans
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
–
–
(3) Test Design
Store Test Design documents
Store Test Cases
Store E2E Scenarios
Store Test Matrix
Store Test Data
(4) Performing Test
Store Test Execution Log
Sore Test Cases Executed in each Test Pass with
Pass/Fail criteria
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
–
–
–
(5) Defect Tracking and Management
Store Description of defects found in each Test Pass
Store Screenshots of the defects
(6) Quantitative Management
Store Number of Defects found in each test pass
(7) Test Reporting
Test Report Results
Store Weekly Status Reports
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
–
–
–
–
–
–
(i) SDLC Documentation
Store any documents related to Software Development Life Cycle
(ii) Peer Review Notes
Store any peer review notes
(iii) QA Meeting Notes
Store any notes related to QA Weekly meetings
(iv) Project Meeting Notes
Store any notes related to Project Meetings
(v) Testing Literature
Store any articles you consider important
(vi) Templates
Store any templates
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for Software Testers
Folder Structure and hierarchy
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers
and QA Leads
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
The following folder structure is based on the CSTE
Common Body of Knowledge
There are a lot of benefits in organizing your data using
this structure
– Files will be stored in a systematic way
– Files will be easy to find
– Historical data for future projects
– Work evidence of your tasks
This folder structure can be tailored to meet your needs
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
The following is an example of the folder structure
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
Description of the folder structure:
– Nemesis Shared Folder
Every team member at Onyx must have a shared folder in
\\Nemesis\General\
– Onyx Project
The folder structure depicts several projects (i.e.,
Washpad, Dragnet, Stardust…) You can start creating
folders for each project you have participated
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
Description of the folder structure:
– CSTE Common Body Of Knowledge
This is the recommended structure to store all your
historical data
– (1) Test Environment
– (2) Test Planning
– (3) Executing The Test Plan
– (4) Test Analysis and Reporting
– (5) Defect Tracking and Management
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
Description of the folder structure:
– Additions to the folder structure
This is the recommended structure to store all your
additions during your daily activities, remember that you
can always tailor this section to meet your needs:
– (i) Templates
– (ii) Outlook Backup
– (iii) QA Website
– (iv) Testing Literature
– (v) Dump
– (..) …
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
(1) Test Environment Hierarchy 1
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
(1) Test Environment Hierarchy 2
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
(2) Test Planning and (3) Executing the Test plan Hierarchy
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
(4) Test Analysis and Reporting Hierarchy
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
This is a brief description of the type of data that you can store in
each folder:
– (1) Test Environment
(1) Test Principles and Concepts (Folder)
– Policy (Folder)
Store the Testing Policy of the project
– Test Strategy (Folder)
Store the test strategy of the project
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managers and
QA Leads
This is a brief description of the type of data that you can store in
each folder:
– Reviews and Inspections (Folder)
In Process Reviews – Inspections, Peer Reviews,
Walk-throughs
Decision Point or Phase End Reviews (Folder)
Post Implementation Reviews (Folder)
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
–
Responsibility chart (Folder)
Store responsibility chart
(2) Development Process (Folder)
– Store any software development documentation
(3) Test Management
– (1) Client Feedback (Folder)
Store any client feedback
– (2) Holidays (Folder)
Store any holidays
– (3) Presentations (Folder)
Store any presentations
– (4) Recognition Awards
Store any recognition awards
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
(3) Test Management
–
–
(5) Task Force Training (Folder)
Store training for team members
(6) Team Meetings (Folder)
Kick off (Folder)
Project Meetings (Folder)
QA Meetings (Folder)
Test Readiness (Folder)
Triage Meetings (Folder)
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
(4) Build the Test Environment (Folder)
– (1) Test Tools (Folder)
Store test tools
– (2) Test Processes (Folder)
Store any processes
(2) Test Planning
(1) Risk Analysis (Folder)
– Store Risk analysis Matrix and documents
–
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
(2)
Test Planning Process
– (1) Pre-Planning Activities
Store test objectives
– (2) Test Planning
–
(1) Estimating (Folder)
(2) Scheduling (Folder)
(3) Staffing (Folder)
(4) Test Plans (Folder)
(3) Post Planning Activities
(1) Configuration Management (Folder)
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
–
(3) Executing The Test Plan (Folder)
(1) Test Design (Folder)
– (1) Test Data (Folder)
– (2) Test Cases (Folder)
(2) Performing Test (Folder)
(3) Defect Tracking and Correction (Folder)
(4) Acceptance Testing (Folder)
Copyright 2006-2007. MSQAA Federation Chapter.
Folder Structure for QA Managersand
QA Leads
–
–
–
–
–
–
(4) Test Analysis and Reporting (Folder)
(1) Status of Testing (Folder)
– Store Weekly Status Reports
– Store Testing Metrics
(2) Test Reporting (Folder)
– Store Test Report Results
(I) Templates
(ii) Outlook Backup
(iii) QA Website
(iv) Testing Literature
(v) Dump
Copyright 2006-2007. MSQAA Federation Chapter.
Q&A
Any questions…
Copyright 2006-2007. MSQAA Federation Chapter.
Reference
CSQA study Guide 2006
Copyright 2006-2007. MSQAA Federation Chapter.
Thank you…
Copyright 2006-2007. MSQAA Federation Chapter.