Independently complete software function testing (1)

Independently complete software function testing

1. Testing Basics

   1. What is software: tools to control the work of computer hardware (page client, code server, data server) (requirements analysis, requirements document, feasibility analysis, outline design, detailed design, coding implementation, product testing, online, operation and maintenance)

   2. What is the function: What problem does the software solve, such as login function, registration function, shopping cart function, etc.

   3. Definition of software:Use technical means to verify whether the software meets the requirements. The purpose of software testing: to reduce defects in software and ensure quality.

   4. Mainstream skills tested

      • Functional testing ☆☆☆☆: Based on the test cases and test data, the execution results of the software are compared with the expected results to see whether the function passes.

      • Automated testing: Use tools or code execution instead of manual testing to check whether access is normal and generate test reports.

      • Interface testing☆☆☆: Use code or tools to test the interface (interface document) provided by the server

        • Hardware interface
        • Software interface: function request to the corresponding code interface

      • Performance testing: simulate the use of software by multiple people and find software server defects

   5. The differences between the 7 test categories:

      1. Stages

         • Unit testing: junit tool, development testing
         • Integration testing: interface testing, testing the access addresses between modules
         • System testing: functional, non-functional (compatibility, documentation) testing
         • Acceptance testing: public testing of special projects (internal beta version), using different groups of people to discover project defects

      2. Source code points

         • Black box testing: (system testing) source code is not visible, only for functional testing, UI functions are visible
         • Gray box testing: (Integration testing) Part of the source code is visible,
         • White box testing: (unit testing) all code is visible, UI is not visible

      3. Special

         • Performance Testing
         • Security testing

   6. Quality model (8 items):

      • What is it: Dimensions to measure a good software (8)
      • Content: functionality, performance, compatibility, ease of use, reliability, security, maintainability, portability

   7. Software testing process:

      1. Requirements review: requirements document, functional analysis and understanding, analysis of core functions
      2. Plan preparation: What to test, who will test it, how to test it (function, performance)
      3. Use case design: Operation document to verify whether the project meets the requirements (use case: case used by the user)
      4. Use case execution: Execute the use case document to implement the test
      5. Defect Management: The process of managing defects
      6. Test Report: Implementation Test Results Documentation

   8. Test case (execution document designed for test projects, function: leakage prevention, test implementation standards) template, 8 elements of test case execution:

      • Use case number: project_module__number
      • Use case title: Expected results (test point)
      • Project/Module:
      • Priority: p0-p4 (p0 is the highest)
      • Preconditions:
      • Test steps
      • Test Data
      • expected outcome

   9. Test case writing case (login function test case):

      use case number	Use case title	Project/Module	priority	Preconditions	Test steps	Test Data	expected outcome
      LA_login_001	Login failed (account is empty)	Log in	p1	1. Open the login page 2. The network is normal	1. Enter your account number 2. Enter your password 3. Click the login button	1. Account: empty 2. Password: 123456	Login failed: account cannot be empty
      LA_login_002	Login failed (account not registered)	Log in	p2	1. Open the login page 2. The network is normal 3. The account is not registered	1. Enter your account number 2. Enter your password 3. Click the login button	1. Account: No registered account 2. Password: 123457	Login failed: account does not exist
      LA_login_003	Login failed (password is empty)	Log in	p3	1. Open the login page 2. The network is normal 3. The account has been registered	1. Enter your account number 2. Enter your password 3. Click the login button	1.Account: registered account 2.Password: empty	Login failed: Password cannot be empty
      LA_login_004	Login failed password)	Log in	p4	1. Open the login page 2. The network is normal 3. The account has been registered	1. Enter your account number 2. Enter your password 3. Click the login button	1.Account: Registered account 2.Password: Wrong password	Login failed password

2. How to write test cases:

   1. Equivalence class division method (solve exhaustion)

      • Description: Divide data sets with certain common characteristics

      • Classification:

        • Valid (choose one): a data set that meets the requirements
        • Effect: Data collection that does not meet requirements

      • step

        • Clarify needs
        • Determine valid and invalid
        • Extract data and write valid classes

      • Case 1: Verify the account and then 6-10 natural numbers (length, type)

        step:
        	1. Clarify needs	6-10 natural numbers
        		length	6-10 people
        		type	Natural number
        	2. Divide valid equivalence and invalid equivalence	efficient	invalid
        		8-bit natural number	3-digit natural number, 12-digit natural number
        			8-bit non-natural number, empty
        	3. Extract data and write use cases	12345678	123	1234567890

        use case number	Use case title	Project/Module	priority	Preconditions	Test steps	Test Data	expected outcome
        LA_001	Legal (8-digit natural number)	account	p0	Open the verification process	1. Enter the account number 2. Click Verify	Account number: 12345678	The account is legal
        LA_002	The account is illegal (3 digits natural number)	account	p1	Open the verification process	1. Enter the account number 2. Click Verify	Account number: 123	The account is illegal
        LA_003	The account number is illegal (12-digit natural number)	account	p1	Open the verification process	1. Enter the account number 2. Click Verify	Account number: 12345689990	The account is illegal
        LA_004	The account is illegal (8-digit non-natural number)	account	p1	Open the verification process	1. Enter the account number 2. Click Verify	Account number: 1234567x	The account is illegal
        LA_005	The account is invalid (empty)	account	p1	Open the verification process	1. Enter the account number 2. Click Verify	Account: empty	The account is illegal

3. plan

   1. Testing basics (2) Testing related knowledge, what is included?

   2. Test design (4) How to conduct the test

   3. Defect Management (1) Discover defects and how to deal with them

   4. Project - Headline (3) Practical Project

4. Software functional testing: Design testing>>>Defects found>>>>Test report (must have quality verification of all software functions)