Content abstract

This eight-chapter book is divided into three parts. Organizationally, we do it not from a technical point of view, but with “Software Test Architect” as the main thread. This book starts with the current situation of the software testing industry in China, helps you analyze your own bottlenecks (Chapter 12), and provides advice for the career planning of software testers. If you want to further develop in testing technology, you can take software testing architect as your career development goal. It also discusses what you need to focus on as a software testing architect and what you don’t need to focus on during testing. The next chapter 5 (3) further explained the software test architects need to master the basic testing techniques and practical soft skills, including software quality model, the types of testing, test methods, test design, exploratory testing, test automation, communication and negotiation, and write the test case expression techniques, to help the reader to software testing the goal of the architect. (chapter 6 ~ 8) after software testing was introduced in detail the architect’s core skills – how to decompose and make test strategy, how to evaluate the quality of the products in product testing and correction test strategy, in terms of the quality evaluation after the ideal test goal, help readers on the way of software testing architects to self cultivation. The book also contains a large number of summary of various testing techniques, which can not only be directly used in the actual test project, but also help readers comb their own test knowledge and establish their own test system.

Test Architect Training: Test Engineer to Test Architect

directory

Part 1: How should software testing engineers plan their careers

Chapter 1 “Three-year Itch” for software test engineers 3

1.1 Brief History of the development of Software Testing 3 1.2 China’s Software Testing industry 4 1.2.1 The overall starting point of software testing is relatively high 4 1.2.2 Difficulties and puzzles of software testing 5 1.2.3 Confused Software testing engineers 7 1.3 Understanding the advantages and disadvantages of software testing 9 1.3.1 Advantages of software testing 9 1.3.2 Disadvantages of software testing 10

Chapter 2 Career Planning for Software Test Engineers 12

2.1 Career Development Direction of Software Testing 13 2.1.1 Development of Software testing in management 13 2.1.2 Development of Software testing in technology 14 2.1.3 “Roles” and “Segments” 16 2.1.4 Development of Software Testing in the field of quality 18 2.2 Suggestions for Career Planning of Software Testing Engineers 2.2.1 Management or technology 20 2.2.2 Suggestions on “job-hopping” of testing 22 2.2.3 Software testing entrepreneurship 23

Part TWO breakthrough: Toward the goal of software test architect

Chapter 3 The DOS and Don ‘ts of software test Architects 29

3.1 What the Software Test Architect needs and does not need to focus on 29 3.1.1 Test architects in requirements analysis 30 3.1.2 Test architects in test analysis and design 32 3.1.3 Test architects in test execution 34 3.1.4 Test architects in test quality assessment 35 3.2 Thinking like a SOFTWARE test Architect 36 3.3 Can the software test manager replace the software test architect 36 3.4 Can the System Architect replace the software test architect 38

Chapter 4 Knowledge capability Model for software Test Architect 40

4.1 Software Product Quality Model 41 4.1.1 Six attributes of software product quality 41 4.1.2 functionality 43 4.1.3 Reliability 45 4.1.4 ease of use 46 4.1.5 Efficiency 49 4.1.6 Maintainability 50 4.1.7 Portability 51 4.2 Test type 52 4.3 Test Method 54 4.3.1 Product Test wheel diagram 54 4.3.2 Functional test method 55 4.3.3 Reliability test method 61 4.3.4 Performance test method 68 4.3.5 Usability test method 72 4.4 Test Design Technique 74 4.4.1 Test Points are Not Equal to Test Cases 75 4.4.2 Four-step Test Design 77 4.4.3 Classification of test points 79 4.4.4 Process Test Design: Path Analysis 84 4.4.5 Parameter Test Design: “Input-output table” analysis 96 4.4.6 Data Class test design: Equivalence class and boundary value analysis 102 4.4.7 Combination class test design: Orthogonal analysis 107 4.4.8 Control Use Case granularity: The combination and splitting of test points 111 4.4.9 Error inference 116 4.5 Exploratory test 117 4.5.1 Basic ideas of exploratory test: CPIE 117 4.5.2 Selecting an appropriate exploratory testing method 118 4.5.3 Conducting exploratory testing 121 4.6 Automated testing 124 4.6.1 Facts to know about automated testing 124 4.6.2 How do YOU evaluate the benefits of automation 126 4.6.3 Introduction to Automatic Test Tools 127

Chapter 5 Software Testing Architect’s Soft Skills 130

5.1 Communication and Negotiation 131 5.1.1 Principles of Communication in Product Testing 131 5.1.2 Use communication to obtain useful information for product testing 134 5.1.3 Communicate with test team members 136 5.1.4 Communicate with leaders or investment decision makers 140 5.2 Write beautiful test cases 141 5.2.1 Test Case Template 141 5.2.2 Test Case Title A Complete sentence 142 5.2.3 Describing Test Case title with Conditions rather than Parameters 143 5.2.4 If a use case contains more than one parameter, The value of each parameter in the test case should be 145 5.2.5 Do not refer to other test cases 147 5.2.6 Avoid excessive user interface details in test cases 149 5.2.7 Clarify the relationship between test steps and expected results 150 5.2.8 Avoid using general words 151 in test procedures

Part three: The core skills of software test architect

Chapter 6 How to Develop a Good Test Strategy 155

6.1 Understanding test strategy 155 6.2 Four-step Test strategy formulation 159 6.3 Product quality assessment model 165 6.3.1 Characteristics of excellent product quality assessment model 165 6.3.2 Software product quality assessment model 167 6.4 Test coverage assessment 167 6.4.1 Requirement coverage assessment 168 6.4.2 Path coverage assessment 170 6.5 Test process assessment 171 6.5.1 Test case assessment 171 6.5.2 Test method analysis 173 6.5.3 Test input analysis 174 6.6 Defect analysis 174 6.6.1 Defect density 174 6.6.2 Defect repair rate 176 6.6.3 Defect trend analysis 177 6.6.4 Defect age analysis 183 6.6.5 Defect trigger factor analysis 188 6.6.6 Combination of defect analysis techniques 190 6.7 Risk analysis techniques 191 6.7.1 Risk analysis 192 6.7.2 Risk Response 196 6.7.3 Analysis of old Functions 198 6.8 Layered testing techniques 201 6.8.1V model 201 6.8.2 Design test levels 201

Chapter 7 Test strategy combat Guide 204

7.1 Initiation 204 7.2 Initial use of the four-step Test Strategy 205 7.2.1 Product quality level 205 7.2.2 Determining the quality level of each feature in the project 206 7.2.3 Risk analysis of the project as a whole 206 7.2.4 Determining the structure of the test strategy 207 7.2.5 Preliminary determination of test layering 208 7.2.6 Review 209 7.3 Development of an overall test strategy 211 7.3.1 Decomposition of product quality objectives 211 7.3.2 Classification of features using old functional analysis 214 7.3.3 Determination of test depth and test breadth based on quality and risk 215 7.3.4 Determining the test priority 218 7.3.5 Determining the overall framework of the test 219 7.3.6 Review 220 7.4 Developing phase test Strategy 222 7.4.1 Test design Strategy 223 7.4.2 Integration Test strategy 230 7.4.3 System Test strategy 234 7.4.4 Acceptance Test Policy 236 7.4.5 Review 238

Chapter 8 Release testing strategy and Product Quality Assessment 240

8.1 Start 240 8.2 Test Policies for Versions 243 8.2.1 Test Scope and Deviations from the plan 243 8.2.2 Test objectives for this version 244 8.2.3 Key Points 245 8.2.4 Test Case Selection 246 8.2.5 Test Execution sequence 247 8.2.6 Tentative Test Policy — Where we need to work together 248 8.2.7 Receiving test policy 249 8.2.8 Review 250 8.3 Tracking test execution 251 8.3.1 Tracking test Case execution 251 8.3.2 Daily defect tracking 256 8.3.3 Adjusting test strategy 262 8.4 Quality assessment 264 8.4.1 Using software product quality assessment models for quality assessment 265 8.4.2 Defect analysis in release quality assessment 271 8.4.3 Adjusting test strategy 273 8.4.4 Establishing feature Version Quality Archives 274 8.5 Later version Test policy 274 8.5.1 Regression Test Policy 275 8.5.2 Exploratory Test Policy 280 8.5.3 Automated Test Policy 283 8.5.4 Review 286 8.6 Stage quality Assessment (including release quality assessment) 287 8.6.1 Stage quality assessment Project 288 8.6.2 Cause analysis of defects found in non-test cases 293 8.6.3 Combination defect analysis 295 8.6.4 Legacy defect analysis 297 8.6.5 Defect repair strategy near release 299 8.6.6 Treatment of non-necessarily recurring bugs 299 8.6.7 Summary 299

conclusion

As a test engineer to own the core competitiveness, efforts to improve themselves is the key, and how to improve, you need to see their own personal learning habits.

Finally, I just want to say that learning will not disappoint anyone, “Test Architect training: Test engineer to test architect” ~ if you support my article, you may wish to forward + comment + follow three links, thank you!