Quality Management Introduction

Download Quality Management Introduction

Post on 11-Jun-2015

100 views

Category:

Software

0 download

Embed Size (px)

TRANSCRIPT

<ul><li> 1. SETA International Quality Management Introduction Nguyen Thanh Huyen April 2014 1 </li></ul> <p> 2. Contents 1. Company introduction 2. Self introduction 3. Ways used for quality management 4. Types of software testing 5. Automated testing 6. Software Development Processes 7. Training functional testing for DEV 8. QA Training 9. Training creating test matrix 10. Mushi tool 11. Discussion 1. Company introduction 2. Self introduction 3. Ways used for quality management 4. Types of software testing 5. Automated testing 6. Software Development Processes 7. Training functional testing for DEV 8. QA Training 9. Training creating test matrix 10. Mushi tool 11. Discussion 2 3. Company introduction Seta International Vietnam was established in 2013 Now we have 153 staffs including: BSE: 16 members DEV: 108members QA: 26 members Comtor: 3 members Seta International Vietnam was established in 2013 Now we have 153 staffs including: BSE: 16 members DEV: 108members QA: 26 members Comtor: 3 members Japan Vietnam America 3 4. Self introduction My name is Nguyen Thanh Huyen, QA Manager I come from Hanoi I have 9 years of QA experience for Japanese companies My hobbies are traveling and cooking My name is Nguyen Thanh Huyen, QA Manager I come from Hanoi I have 9 years of QA experience for Japanese companies My hobbies are traveling and cooking I love my job because its very challenging and it's also great when QA involved projects get high quality and praises from customers My team has 29 members. All of them are skilled and professional 4 5. Ways used for quality management 1. For the Project Explaining SRS(*1) and checking specification comprehension of developers (by review functional testing for DEV) Analyzing &amp; confirming &amp; controlling CR(*2) Applying appropriate types of software testing for each project Applying automated testing to minimize workload Applying flexible process for each project 2. For Member DEV: ProjectsTraining functional testing for developers QA: Training QA members methodically: tester --&gt; SQA(*3) --&gt; QAE(*4)--&gt; PQA(*5) --&gt; QAL(*5) 1. For the Project Explaining SRS(*1) and checking specification comprehension of developers (by review functional testing for DEV) Analyzing &amp; confirming &amp; controlling CR(*2) Applying appropriate types of software testing for each project Applying automated testing to minimize workload Applying flexible process for each project 2. For Member DEV: ProjectsTraining functional testing for developers QA: Training QA members methodically: tester --&gt; SQA(*3) --&gt; QAE(*4)--&gt; PQA(*5) --&gt; QAL(*5) 5 6. Types of software testing Smoke testing GUI testing Functional testing Exploratory testing API testing Scenario testing Bug fixed testing Regression testing Acceptance testing Performance testing Load testing Stress testing Security testing Regression testing Smoke testing GUI testing Functional testing Exploratory testing API testing Scenario testing Bug fixed testing Regression testing Acceptance testing Performance testing Load testing Stress testing Security testing Regression testing 6 Manual test Auto test 7. Automated testing (1/2) Web PCs auto test tool Selenium Jmeter AOS apps auto test tool Robotium iOS apps auto test tool UI Automation iOS &amp; AOS apps auto test tool Calabash Test Cloud Service Web PCs auto test tool Selenium Jmeter AOS apps auto test tool Robotium iOS apps auto test tool UI Automation iOS &amp; AOS apps auto test tool Calabash Test Cloud Service 7 8. Automated testing (2/2) When to apply: Regression testing should be performed Testing on many devices or platforms Objects of automated testing must be stable applications Why: Improve test efficiency Improve the regression test Minimize workload Resource utilization Easily reproduce bugs When to apply: Regression testing should be performed Testing on many devices or platforms Objects of automated testing must be stable applications Why: Improve test efficiency Improve the regression test Minimize workload Resource utilization Easily reproduce bugs 8 Testing time decreases 60.4% when auto testing is applied for regression test. (5 devices, 20 scenario test cases, 20 time regression test) 9. Software Development Processes SPRINT 1 Make test cases Fixed bug &amp; re-test Coding Test &amp; fix bugs &amp; re- test Review Test cases MakeTest cases Test &amp; Re-test Review Test cases Review source Test &amp; Re-test Customer Confirm Flexible: Comfirm every sprint BSE DEV QA ALL Customer 9 Proposal Preparat ion Review Test cases Review source Test &amp; Re-test SPRINT 2SPRINT 2 SPRINT nSPRINT n Closing Flexible: Comfirm every sprint Common:Confirm at end of Sprints Customer Confirm OK NG 10. Communication in Project BSE Hanoi BSE Tokyo Japanese Japanese 10 Customer DEV DEV DEV QA QA QA Japanese Vietnamese 11. Training functional testing for developers Why: Making sure programs are installed correctly according to specifications Making sure programs run correctly in valid cases Making sure NO functional bug released to QA How: Spec Create FT Coding FT AT Customer Developer QA/BSE Why: Making sure programs are installed correctly according to specifications Making sure programs run correctly in valid cases Making sure NO functional bug released to QA Customer Developer QA/BSE 11 Number of bugs decreases 60% when functional testing is applied for development team. 12. QA Training Training creating test matrix Training reporting &amp; analyzing &amp; confirming bugs Training reviewing functional testing of developers Training auto test tools Training project management Training Software Development Processes Building common test view points (400 points) and test experiences Making test-cases auto-generating tool (Mushi tool) Training Japanese Training creating test matrix Training reporting &amp; analyzing &amp; confirming bugs Training reviewing functional testing of developers Training auto test tools Training project management Training Software Development Processes Building common test view points (400 points) and test experiences Making test-cases auto-generating tool (Mushi tool) Training Japanese 12 13. Training creating test matrix Entrance Ceremony Explain meeting Excite Entrance Ceremony Explain meeting Excite Test design preparation Specification preparation reviews Specification reviews Test design preparation Specification preparation reviews Specification reviews Test design matrix Add QA-ID Create matrix Review matrix Update matrix Test design matrix Add QA-ID Create matrix Review matrix Update matrix Test cases Create test cases Review test cases Update test cases Test cases Create test cases Review test cases Update test cases Graduation exercises Graduation exercises 13 Entrance Ceremony Explain meeting Excite Entrance Ceremony Explain meeting Excite Test design preparation Specification preparation reviews Specification reviews Test design preparation Specification preparation reviews Specification reviews Test design matrix Add QA-ID Create matrix Review matrix Update matrix Test design matrix Add QA-ID Create matrix Review matrix Update matrix Test cases Create test cases Review test cases Update test cases Test cases Create test cases Review test cases Update test cases Graduation exercises Graduation exercises 1 week 1 week1 ~ 2 weeks 14. Mushi tool 14 Creating time decreases 40% when Mushi tool is applied for creating test cases 15. Discussion 15 16. Appendix SRS(*1): Software requirements specification CR(*2) : Change request SQA(*3) : Software Quality Assurance QAE(*4): QA engineer (auto test tool) PQA(*5): Process Quality Assurance QAL(*5): QA Leader SRS(*1): Software requirements specification CR(*2) : Change request SQA(*3) : Software Quality Assurance QAE(*4): QA engineer (auto test tool) PQA(*5): Process Quality Assurance QAL(*5): QA Leader 16 17. Thank you for your listening!!! 17 </p>

Recommended

View more >