Fundamentals of software testing

** If there is a mistake , Thank you for correcting **

If there is a mistake , Thank you for correcting , Please send a private message to the blogger , There is a red envelope for hard work , Worship “ one-word teacher ”.

Please find the paragraphs you need according to the table of contents

Introduction ： This blog is organized for individuals Java Learning notes , If there is a mistake , Thank you for correcting . System learning , Welcome to continue to pay attention , Follow up updates ~
Java communication qq Group 383245788. There are some resources and leaders in the group , Welcome to exchange .

This article aims to learn and communicate , Personal software testing basic learning experience

Introduction learning , Continuous updating

software test

Software testing theory

Software test classification

According to the test phase

unit testing ： Also called module testing , For the smallest unit in software design - Program modules , Test for correctness check . Unit testing needs to design test cases from the internal structure of the program . Multiple modules can be tested independently in parallel .
Unit definition :C Middle refers to a function ,Java Middle refers to a class , In graphical software , Unit generally refers to a window ,1 Menu .

Integration testing ： It's also called assembly testing , Usually on the basis of unit testing , Put all program modules in order 、 Incremental testing . Focus on testing the interface part of different modules .

The system test ： Test the whole software system as a whole , The test is based on the requirements specification . It's time for system testing , Software is basically molded .

The acceptance test ： Verify whether the software meets user requirements .
α test

• Alpha Internal version
• Usually only communicate internally
• Generally speaking ,bug More .

β test
Bate Public beta version , The beta version is open to all users for free .

γ test
Gamma edition , Close to the official release .

According to whether you need to view the source code classification

Black box testing ： Also known as data-driven testing , The internal structure and characteristics of the program are completely ignored , Focus on the functional requirements of test software , Only care about the input and output data of the software .

White box testing
Not only focus on functions , Also pay attention to how the code is implemented .

Grey box testing
A test between black box and white box

Sort by whether to run

The static test
Software not allowed , Statically observe whether the software meets expectations

Dynamic testing
Running software , Test during operation

Sort by automation or not

Manual testing
Test the software manually by test engineers

automated testing
Automatically test whether the software has bug

Other categories

Smoke testing
Make a rough test of the most basic process and work of the software , See if the most basic process can run through .

regression testing
When repairing a bug after , Put the previous test cases , Under the new code , Test again .

Random test
Important functions for software , Retest

Exploratory testing
General understanding and learning projects , While testing the project .

Software quality model

• Software quality , It is the degree to which software is consistent with clearly and implicitly defined requirements .
• ISO 9126 Software quality model is an international standard for evaluating software quality , This model is the core of software quality standards , For most software , You can consider from here 6 Two features and 27 Sub features to test 、 Evaluate a software .
  

• Functionality
  The correctness of the function 、 Functional security 、 Functional compliance
• reliability
  Software should have fault tolerance 、 You can recover quickly after an error occurs
• Ease of use
  Is the software interface a process 、 Whether the prompt is friendly 、 Whether the user uses the function properly
• efficiency
  Software must be efficient
• Maintenance
• Portability
  Adapt to different systems

Software development process model

• In the decades of software development practice , Many software development models have gradually formed to describe and represent a complex development process , Like the waterfall model 、 Rapid prototyping model 、 Spiral model .
• Software testing is closely related to software development patterns , Software testers should fully understand the development mode of software , In order to find your position , So as to play their own value .

• Waterfall model

1. Demand analysis
   R & D analysis requirements specification
   Judge the realizability of requirements
2. Outline design
   Use specific technical points
   Roughly divided into modules
3. Detailed design
   Detailed enough to support coding
   Class and class relationship , Class design
   Function design
   Details of each interface
   Database table relationships , Field relationship
4. code
   The coding operation depends on the detailed design
5. software test
6. Software maintenance
   After the software goes online, it needs continuous maintenance

• Characteristics of waterfall model
  Linear model , Each step is performed in sequence
  Document driven , Document output at each step
• The advantages of waterfall model
  Each stage of development is relatively clear
  After the completion of the current phase , Just focus on the next stage
• Disadvantages of waterfall model
  Rely on early demand surveys , Do not adapt to changes in demand
  Risks are often delayed , Lose the opportunity to correct early

• Rapid prototyping
• characteristic ：
  Quickly build software prototypes
  Support user participation
• advantage ：
  Overcome the shortcomings of waterfall model , Better meet the needs of users and reduce the project development cost caused by unclear software requirements
• shortcoming ：
  Not suitable for the development of large systems （ Suitable for developing small , Flexible systems ）

• Spiral model
  
• Characteristics of spiral model
  Risk assessment activities have been introduced
• advantage
  The spiral model is largely a risk driven methodology
• shortcoming
  Adopting the spiral model requires considerable experience and expertise in risk assessment

Test process model

The test case

Test case design method