iotap software build process author: aman choudhary draft version – work in progress
TRANSCRIPT
IOTAPIOTAPSoftware Build Process
Author: Aman ChoudharyDraft Version – Work In Progress
Standards & Standards & DocumentationDocumentationA. Software Coding Standards
• A set of rules for writing software codes
• Generally defined by the customer
B. UI Standards• CSS Classes or Fonts, Table Sizes, etc which are defined by the
UI Designer
• Generally defined by the customer
C. Smoke Test• A set of rules which the Project Lead needs to execute before
the software is released to QA for it to starts its Testing
• Defined jointly by the customer and IOTAP Team Lead
Roles & Responsibilities Roles & Responsibilities (IOTAP)(IOTAP)
1. Team Lead◦ Overall Customer Satisfaction
◦ Monitor Software developed is meeting standards (UI & Software Coding)
◦ Enforce Development Release Process
◦ Time Sheets Are Being Entered
◦ Develop & Perform Smoke Test
◦ Automate Test Cases
2. Software Engineer◦ Develop Software Per Decided Software Coding Standards & UI Standards
3. QA Engineer◦ Test Software To Make Sure It Meets Specifications
4. Executive Sponsor◦ Weekly Progress Report From Software Team Lead
Software Code RepositorySoftware Code Repository
Current Software Branch
Production Software Branch
Sample Repositories IOTAP has used: - Source Safe - Sub Version - Team Foundation Services
Staged Test Instance: May 7th, 2007 Build
5. Promote:Test To Prod
1. Promote:Dev To
Test
2. PerformSmoke Test
3. PerformQA
Staged Test Instance: May 20th, 2007 Build
5. Promote:Test To Prod
Development & Production Development & Production BranchBranch
Current Software Branch
May 3rd, 2007
May 5th, 2007
May 7th, 2007
…..
….
….
…..
May 1st,, 2007
May 1st,, 2007May 1st,, 2007
Production Software Branch
May 7th, 2007May 7th, 2007
May 20th, 2007May 20th, 2007
….
….
…..
1. Promote:Dev To
Test
2. PerformSmoke Test
3. PerformQA
Staged Test Instance: May 1st, 2007 Build
5. Promote:Test To Prod
1. Promote:Dev To
Test
2. PerformSmoke Test
3. PerformQA
4. PerformUAT
4. PerformUAT
4. PerformUAT
May 20, 2007
QA Issue Tracking (Cont.)QA Issue Tracking (Cont.)1) Title
2) Status Open Need More Information Unable To Reproduce In Progress Ready For Testing Closed
3) Assigned To
4) Created By
5. Priority Show Stopper High Medium Low
6. Build Reported
7. Build Fixed
8. Comments
9. Attachments
QA Issue Tracking QA Issue Tracking 1) Open
2) Work In
Progress
1.b) Unable To
Reproduce
1.a) Need More
Information
3) Ready For
Testing
4) Closed