On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
For IBEEeCom Portal Testing
Name Role Date
Prepared By Kareemulla Sk TL 10/04/2008
Reviewed By Rama Krishna P Test Manager 14/04/2008
Approved By Srinivasa Rao Quality Analyst 17/04/2008
Sno Date Version No Page No Mode Description of
A-Added, M-Modified, D-Deleted
Software Structure is a hierarchical folder structure into which the process
documents are stored. Software Structure allows users to store and maintain the
process documents in an easy and efficient way. This approach helps in easy
identification and retrieval of documents.
2. Folder Structure
2.1 The project Folder Structure
We have to follow the below steps to create a Tester’s Drive for IBEEeCom Project
Below Diagram shows the Project (Main) folder structure with the name of ‘IBBE
Steps to create:
1. Create a folder named “IBEEeCom”
2. Create sub folders named “Admin”, “User”, Templates and Pro-doc within the
“IBEEeCom” folder as below diagram 01.
Admin is a module under IBEEeCom, all Project Trainees are recommended to put
their ‘Admin module’ related documents into Admin Folder.
User is a module under IBEEeCom, all Project Trainees are recommended to put
their ‘User module’ related documents into User Folder.
In Templates Folder we have to store all Testing Templates (ex: Test case, Defect
We can use Pro-Doc (Process Documents) folder to store all Testing Process Related
Documents (ex: Test Strategy, Test Plan etc.).
2.2 Admin Module Structure
The Below diagram depicts the Admin folder structure within the “IBEEeCom Project
Admin- Admin module
Requirements- for storing requirements documents (ex: BRS, SRS etc.)
R-Reports- we have to use this folder for storing Review Reports.
CR- (Change Requests) for storing any change requests from customers.
Builds- for storing Build versions
TC-D-(Test Case Document) we have to use this folder for storing Admin module
Test case Document.
DP- (Defect profiles) we have to use this folder for storing Defect Reports.
Automation- we should use this folder for storing Automation related docs
Time sheets- for storing testers work status reports.
Others- we can use this folder to store any other docs than above mentioned
2.2.1 The Below diagram shows the Automation folder structure within the “Admin
Automation is a sub folder under ‘Admin Folder’.
QTP- (QuickTest Professional) we have to use this folder for storing Functional Test
Automation related docs.
LoadRunner- we have to use this folder for storing Performance Test Automation
2.3 User Module Structure
User module folder Structure is also same like Admin folder so we can follow above
Procedure to create the User module folder.
Note: As it was a web application Client side Installation not required so testers
no need to download and Install Builds. Application can be deployed at Server side
and any build modifications also Server side only. Testers will get Information about
every build modifications.
Testers are recommended to create the Project Folder first, and then they have to
put this folder in the Configuration Management tool (Visual Source Safe).
Testers have to download required documents from the Server with respect to
System Administrator’s instructions.