Big talk Software Testing

Big talk software testing (No distortion, no deformation, no obscure, no flicker, clear software testing, where to come, where to go. Laruence and Tom give you insight into the bottom layer of the software architecture and explain the design philosophy of software testing.)

Edited by olec Hejin Chi

ISBN 978-7-121-24097-3

2014Published in September

Pricing: 45.00 RMB

280Page

16Open

Edit recommendations

This book uses a complete and rigorous knowledge system and humorous language to lay a solid foundation for your software testing; cultivate your keen insight and excellent testing qualities, improve your skill and face software development/testing with ease.

Contents

Big talk software testing organizes and explains all aspects of software testing with multiple small stories, cases, and cartoons through interesting conversations between little white and Big Bird, includes test requirements, test categories, test plans, and test management.

Although the expression of "big talk" is "big talk", the content structure is rigorous. In the process of explaining software testing, the learning threshold is reduced through the inquiry structure, which makes it easier for readers to understand the purpose, strategy, method, and management of testing, clarify common misunderstandings about software testing, and express the true meaning of testing in a way that is not distorted, not distorted, not obscure, and not fooled, so as to not only give it a "fish ", in addition, the goal of "fishing" is to guide readers to understand the great wisdom contained in the software testing process.

Big talk software testing is suitable for software testing, software development and software management personnel as well as other computer enthusiasts.

Directory

Part 1 software requirements and Design 1

Chapter 2 software requirements 2

1.1 From the ambiguity of requirements to the purpose of software testing 2

1.2 definition and classification of requirements 5

Chapter 2 PRD review 8

2.1 PRD Category 8

2.2 software product positioning 9

2.3 software product requirements 14

2.4 audit software product requirements 17

2.5 range constraint 26

Chapter 29 user story 29

3.1 What are user stories 29

3.2 user story features 30

3.3 split, refine, and merge user stories

Chapter 4 Audit FS 35

4.1 obfuscation 35

4.2 Delivery objective 36

4.3 range constraint 37

4.4 hypothesis and dependency 37

4.5 function description 38

4.6 audit function description 38

4.7 non-function description 41

Part 1 software functional testing 43

Chapter 4 accuracy and suitability of functional testing 44

5.1 functional testing concept 44

5.2 classification of functional tests 45

5.3 suitability test 45

5.4 Accuracy Test 46

Chapter 4 software functional testing user story 47

6.1 software functional test story 47

6.2 performer/behavior/status/expected results/Check Point 48

Chapter 2 software interoperability testing 72

7.1 definition of interoperability testing 72

7.2 differences between compatibility and interoperability 73

7.3 cause of unavailability 74

7.4 interoperability test classification 75

Chapter 1 Security Testing 81

8.1 software security testing concept 81

8.2 software security testing policy 82

8.3 user authentication security 84

8.4 System Network Security Test 89

8.5 Database Security Test 94

Chapter 1 Globalization Test 99

9.1 globalization Test Category 99

9.2 date 101

9.3 character format 103

9.4 numeric format 104

9.5 Input Method Editor test 106

9.6 language sensitive information testing 107

Part 1 software non-functional testing 3rd

Chapter 1 usability testing 10th

10.1 usability test classification 110

10.2 Comprehension Test 111

10.3 learning habits test 113

10.4 ease of operation testing 114

10.5 UI test 121

Chapter 1 reliability testing 11th

11.1 fault tolerance test 126

11.2 recoverability testing 127

11.3 failover test 130

Chapter 2 portability testing 12th

12.1 portability test definition and classification 131

12.2 user story list 131

12.3 behavior/status/expected results/Check Point 133

Chapter 2 Performance Testing 13th

13.1 differences between functions and performance 143

13.2 performance testing indicators 144

13.3 obtain performance requirements 148

13.4 Performance Test classification 149

13.5 how to perform performance testing 151

13.6 analysis performance bottleneck 152

Chapter 4 document testing 14th

14.1 document test importance 156

14.2 document types 156

14.3 document test checkpoint 157

Part 1 software project processes and risks 4th

Chapter 2 software project development process 15th

15.1 project milestone definition 160

15.2 main phases of software projects 161

15.3 R & D cycle formulation 170

15.4 workload estimated 171

Chapter 2 Project Risk Analysis 16th

16.1 differences between risks, problems, and defects 177

16.2 risk classification 177

16.3 risk analysis 183

16.4 risk mitigation 184

16.5 common risk handling measures 186

Part 1 test strategy and test plan 5th

Chapter 1 test policy 17th

17.1 definition and classification of test policies 191

17.2 testing focus/testing priority analysis 192

17.3 testing strategies for each time stage 193

17.4 testing policies for multiple platforms, operating systems, and browsers: 198

17.5 testing start and end Criteria 198

17.6 test environment policy 201

17.7 tester-specified policy/task allocation policy 203

17.8 test tool usage policy 205

17.9 test report/progress policy 205

Chapter 1 test plan 18th

18.1 definition of test plan 206

18.2 scope of the test plan: 207

18.3 Test Case Design Method 207

18.4 priority of test cases: 217

Part 1 Software Test Management 6th

Chapter 1 How to Prevent bugs 19th

19.1 difference between bug and defect 220

19.2 significance of bug prevention 221

19.3 clean code 222

19.4 code reusable 224

19.5 code review management mechanism 227

19.6 Perform unit testing 227

19.7 code reconstruction 228

Chapter 1 How to log high-quality bug 20th

Who should write the 20.1 bug report to? 232

20.2 bug template Introduction 232

20.3 Common Bugs 246

20.4 how to analyze root cause 247

20.5 bug lifecycle 251

20.6 test report analysis 253

Chapter 2 other QA routine work 21st

21.1 daily report 255

21.2 how to hold a meeting 258

Postscript QA self-cultivation 261

What does QA do in Lesson 1st? 261

Question and reflection in Lesson 2nd 262

3rd QA skills 264

4th relationship between QA and Dev 265

Main Contribution of 5th QA 266

6th relationship between automated testing and routine testing 267

Author Profile

Olec: IBM senior Test Engineer

Preface

The entire article of this book is based on a situational dialogue. It organizes and explains software testing with multiple stories, cases, and cartoons. From the perspective of software demand design, after properly classifying software testing, the content of this book is divided into the following aspects.

In terms of test requirements: how to test requirements, how to review requirements, and how to design documents.

In terms of test classification: Describes the checkpoints of the six features and 27 sub-features of the software quality model, and provides experience and cases so that readers can easily use them in the actual project environment; let readers clearly know what software testing is?

In terms of test plan: How to Write user stories, test cases, test plans, test modeling, and human resource allocation plans.

In terms of Test Management: how to predict risks, how to write daily reports, how to communicate with Dev (R & D) and PM (Project Manager), and how to manage test projects, how to use Automation Technology to Improve testing efficiency.

Although the expression of this book is "big talk", its content structure is rigorous. In the process of explaining software testing, the learning threshold is reduced through the inquiry structure, which makes it easier for readers to understand the purpose, strategy, method, and management of testing, clarify common misunderstandings about software testing, and express the true meaning of testing in a way that is not distorted, not distorted, not obscure, and not fooled, so as to not only give it a "fish ", in addition, the goal of "fishing" is to guide readers to understand the great wisdom contained in the software testing process.

This book is different from other software testing books with the following main features.

Fine

Due to the special nature of software testing, software testers should be more careful, patient, meticulous, sensitive, and other personality elements, involving a lot of aspects, relatively basic, but also relatively fine. Taking software installation as an example, a complete software installation checkpoint includes: 1. check the installation environment; 2. the installation is interrupted. 3. check for backtracking; 4. customizable installation; 5. install specific parameters/port dependencies; 6. installation path; 7. installation media; 8. installation language; 9. install shell; 10. install components. 11. operating system compatibility; 12. OS Language Pack; 13. hardware system compatibility; 14. logic installation sequence; 15. installation Security; 16. installation interface; 17. check the installation result.

Therefore, this book summarizes these small knowledge points and checkpoints, so that readers can follow the rules and easily perform tests based on the illustrations. This book uses four levels of titles, each of which is a practical case, to effectively solve the actual problems encountered by readers.

Deep

When it comes to testing, people first think of testing as a technology. However, in fact, testing is a philosophy and an idea behind which is a person's vision and world view. A test may reveal the tester's quality and ability to view and think about problems in many aspects. The popular test books on the market do not do enough in terms of professional classification. Because of this, this book is pursuing good guidance and deep understanding, focusing on the essential understanding of software testing technology, instead of simply explaining the test.

Guang

Popular software testing books on the market only focus on software functional testing, while ignoring the extended content of software testing, such as usability testing, performance testing, and document testing in non-functional testing. With the increasing demand for ease-of-use and reliability, this book provides a detailed analysis of the above aspects, and works out a test scheme based on a large number of cases to meet the needs of readers.

Happy

A hard-pressed team can't make love products, and pleasant programming and happy testing can make your career a long way. Therefore, this book is humorous and contains comics to present facts and make sense, and strives to add a touch of light to many rigorous Software Test books.

 

This book is not a omnipotent book, but it must be a good assistant and partner for your software testing, development, and management work.

This book is mainly prepared by ou LiQi and he jinchi. Other participants include Liu Yang, Qin Xiaodong, Li qigao, Ma Xue, Ma Yu, Ma Hu Jun, Li Fuxing, And Niu Yongjie.

Finally, I would like to thank some important people who have supported the compilation of this book, and I sincerely thank you for your assistance.

 

Big talk Software Testing