[test development] software testing - concept

Measuring the results of software testing —— demand

Before we know what requirements are , Let's first understand how software was born ️️

How software was born

What is demand

1. Documents that meet user expectations or contractual requirements （ contract , standard , standard ） Conditions or permissions required , It includes User requirements and software requirements .
   User requirements are simple , Software requirements are the refinement of user requirements , Specific implementation details , Document .
2. Requirements are the basis for testers to carry out software testing

The relationship between software requirements and user requirements ： Software requirements are transformed from user requirements

The concept of test cases

A test case is a set of sets initiated to the system under test , This set includes Test environment , Test data , testing procedure , Expected results （ title , Importance , Function module , priority , Whether it is manual, etc ）

Let's better understand test cases through a case ：

What is? BUG

If and only if Software requirements specifications （ Software requirements document ） Existing and reasonable , The function of the software does not meet the requirements specification , It's a software error （BUG）;
If the software requirements specification does not exist , that The needs of users exist and are reasonable , The function of the software does not conform to the user's requirements is a software error （ BUG）.

Five models of software development and two models of software testing

The life cycle of software development

Demand analysis —— plan —— Design —— code —— test —— Operation and maintenance

Five models of software development

1. Waterfall model
   
2. Spiral model ： Suitable for large projects , complex , High risk projects
   
3. Incremental model 、 Iterative model （ Usually put them together and say ）： Strong anti risk ability
   
4. Agile model
   characteristic ：
   
   Classic agile processes ：scrum technological process
   Before we learn agile processes , Let's first understand these roles ：
   1）PO—product owner : The product manager , Responsible for collecting requirements , Turn into user story
   2）SM—scrum master : project manager , Be responsible for ensuring the implementation of this agile process
   3）ST : R & D personnel with various skills —— test , Research and development ,UI etc.
   Scrum technological process ：
   1） Product launch meeting : PO Put it in order user story Explain , Prioritize , Find out what constitutes this iteration with high priority , Formation sprint backlog
   2） Iteration planning meeting ： SM and ST People work together to analyze the requirements to be iterated in this period , Task allocation and time estimation
   3） Daily station will ： What did you do yesterday , What's the problem , Today's plan
   4） Product presentation ： Demonstrate products to customers , Explain , Sort out the deficiencies and the modification suggestions put forward by the customer into user story Put it in the next iteration
   5） Retrospective meeting ： Review this agile process , Find out the bad places , Next iteration improvement , Optimize agile processes

Two models of software testing

V Model

W Model （ double V Model ）