Manual (functional) test 1

Software quality

Application scenarios ： Provide a way of thinking about software products from the perspective of testing

• Define whether the actual product requirement description is consistent , A high degree of consistency means that the quality meets the demand （ good ） 
• How to judge the quality of software ？                       
• function ： Whether the software product has some ability                   

Supported by a mobile phone 5G  

•   performance ： The occupancy of software products for speed and space

  Fast , Small occupation

•   Compatibility ： The ability of software to be compatible with other types of software and hardware

  The famous "3Q" War

• reliability ： Whether the software has the ability to solve a problem
• Security ： Whether data transmission and storage are safe during software operation

  It belongs to special test , The demand is higher

•   Portability ： The ability of software products to migrate from one environment to another
• Maintainability ： After the software fails , Self repair / The ability to recover

The life cycle of software

The process of software from scratch to extinction

Also called software development process model , Software life cycle model

  The advantages of waterfall model

• Each stage is clear , And there are corresponding documents
• When a phase is complete , Just start the later stage （ disposable ）

  Disadvantages of waterfall model

• The time to find the problem is relatively late , Lose the opportunity to correct mistakes in advance
• The test intervention is relatively late

  Applicable scenario

• It is applicable to large projects whose requirements are not easy to change

 [ Expand ] Agile development model

Be able to adapt to changes in demand , And can give a fast response

•     Small step run
• Acp  

  Software test model

v Model

effect ： More detailed description of the test process , Corresponding production . The relationship between development

 

 v Model advantages

Each stage is clear , The testing process consists of the bottom layer （ Code ） Test to the top （ Testing process ）

V Model shortcomings

Not applicable to requirements change

w Model

effect ： More detailed description of the test process , Corresponding production . The relationship between development is clearer

 

 w Model advantages

• The test intervention time is early , Be able to find problems in time , Reduce repair costs
• Testing accompanies the whole software production cycle , In addition to testing software testing , You also need to validate the document

 w Model shortcomings

• The model has high complexity in application （ Computer skills , Professional capability , Ability to manage , Test quality ）

  The test case

Purpose  

• Easy to test and verify （ Divide a large number of requirements into small test points ）
• The comprehensiveness of the test （ Subsequent tests can be used directly ）
• The test quantifies

  Definition

The test case , Also called Test Case, A set of test inputs designed for a specific purpose , Documentation of execution conditions and expected results

 

  Test case design method

How to write test cases ？

  Division of equivalence class

• Equivalence class definition
• In the batch test data , Select a subset of data with common characteristics as the test input
• Classification of equivalence classes
• Effective equivalence class ： Data that meets the needs
• Invalid equivalence class ： Test data that does not meet the requirements

  Steps of designing use cases by equivalence class partition method

Case study ： How to test the sum of two two digit integers （ namely -99z To 99 Sum the data between ） No problem ？

Clear requirements

  Test purpose

     eg: Verify whether two digit integers can be summed normally

  Testing conditions

 eg:

• No more than two digits
• Integers . Letter . chinese . Symbol . Space . empty     

•   length
• type （ From keyboard input ）
• The rules

Divide equivalence class

Effective equivalence class  

 eg:-10,30

  Invalid equivalence class

eg: Contain letters . chinese . Symbol . Space . empty

• Extract data and write test cases
• Fill in the content as required through the test case template  

  Equivalence classes apply to scenarios

• It is common for tests with batch data input , Applicable when exhaustive testing is not possible
• Common representatives ： Input box （ A drop-down box . Selection box , Drop down list, etc ）

  Considerations for writing use cases

• Single module test , The use case title is unique
• The necessary steps are as clear as possible
• The expected results try to describe the statements and phenomena of test associativity （ If there is a specific phenomenon, the best description ）

  Case number and test item abbreviation are set accordingly