Software Testing

The individual needs to know and understand:

• The purpose of software testing
• The purpose and nature of standards, the industry’s standards, and procedural specifications for software testing
• Corresponding requirements generated by software testing activities
• Entry and exit requirements for software testing
• Testing requirements for each quality characteristic
• Procedures and processes for identifying, analysing and evaluating information from a variety of sources
• The importance of correct project scheduling and resourcing
• Common risks in testing activities and corresponding preventative measures
• The interfaces for division of responsibilities between different testing roles
• The importance of collecting, summarising, and accurately describing problems
• Principles of confidentiality for customer information security
• The importance of self-responsibility and stress resistance
• The importance of improving team capabilities and motivating team members
• The importance of environmental awareness and sustainable practices.

The individual shall be able to:

• Plan each testing phase and testing activities according to the software testing accepted process
• Use research techniques and skills to keep up to date with industry standards and new technologies
• Prepare test process documentation that complies with test standards and specifications
• Determine whether the software meets entry and exit requirements
• Conduct testing using testing techniques according to the requirements of each quality characteristic
• Check whether the planned work meets the needs of customers and the organization
• Plan and allocate testing tasks and resources in a team environment to ensure successful completion of the testing project
• Prepare risk plans based on the actual situation of each test assignment
• Allocate test tasks and follow up the progress and quality of each task
• Collect, summarise, and describe problems, applying them to the entire testing process: requirement confirmation, discussion of solutions, and defect compilation
• Optimise sustainable practices, with particular attention to greenhouse gas emissions, resource consumption, and electronic waste.
• Maintain the integrity and confidentiality of data, information and documents, and comply with confidentiality requirements for data storage and transmission
• Conduct testing to the requirements of objectivity, impartiality, rigour, meticulousness, and disciplined curiosity
• Reflect on personal and team performance and set challenging new targets.

The individual needs to know and understand:

• The importance of listening as part of effective communication
• The roles and requirements of colleagues and the most effective ways to communicate
• The importance of developing effective working relationships with colleagues and managers
• What constitute effective teamwork skills
• Skills and techniques to resolve misunderstandings and conflicts, and solve problems during tension and conflict
• The importance of staying calm and expressing oneself carefully and accurately
• The importance of inspiring and guiding ideas.

The individual shall be able to:

• Listen to customers’ needs to help set out clear test requirements and deepen their understanding of tests’ purposes and benefits
• Maintain effective oral, written, and digital communication with colleagues and managers, and communicate efficiently
• Contribute to developing a strong and effective team, sharing knowledge and expertise with colleagues, helping to develop a culture of mutual support and learning, and continuously improve testing skills
• Maintain a positive demeanour and proactively support others to resolve problems during times of tension and conflict
• Describe and explain one’s intentions accurately, with clear logic, checking to ensure understanding without ambiguity
• Give customers confidence and guidance, with suggestions and consultation as necessary, such as when change is required in their thinking or approach.

The individual needs to know and understand:

• Methods of software testing requirements analysis
• The principles of formulating test indicators such as performance testing and reliability testing
• The requirements of the test environment
• Test preparation
• The requirements of test plans and programs
• The changes that are possible and acceptable
• Configuration management requirements.

The individual shall be able to:

• Analyze, extract and summarise test requirements and obtain customer approval
• Help customers determine a reasonable test scope and test indicators
• Build test environments by oneself
• Assist developers to build test environments
• Carry out or promote test preparation work, including but not limited to (for example) data initialisation, test account creation, and business training
• Prepare test plans and programs, and make reasonable plans for (for example) project tasks, progress, personnel, communication mechanisms, risk management, configuration management, change management, defect levels, and test strategies
• Take countermeasures in advance for possible changes
• Plan project configuration management.

The individual needs to know and understand:

• The business model of the software under test
• The key points and difficulties of each test type, including
  • functional testing
  • performance testing
  • security testing
  • reliability testing
  • compatibility testing
  • maintainability testing
  • usability testing
  • portability testing
  • automation testing
  • mobile application testing
  • white box testing
• The principles of test case priority division
• Common test case design methods, such as equivalence class, cause-and-effect diagram, decision table, error guessing method, and scenario method
• Commonly used performance testing, security testing, automated testing, code auditing and other tools, and master mainstream programming languages such as Java, Python, and JavaScript
• The preparation and debugging of automated test scripts
• The preparation and debugging of performance test scripts
• The preparation of interface test scripts
• The design methods of white-box test cases, including statement coverage, judgement coverage, logic coverage, condition coverage, and path coverage
• The content and writing requirements of test cases.

The individual shall be able to:

• Design use cases based on the characteristics of the business model to ensure test case coverage
• Clarify the test focus and test difficulties according to different test types, and improve the test cases in a targeted manner
• Prioritise test cases based on the business of the system under test
• Design test cases using common methods such as equivalence classes, cause-and-effect diagrams, decision tables, error guessing methods, and scenario methods
• Prioritize test cases on a well-reasoned basis
• Use common testing tools and corresponding programming languages to design and debug test scripts
• Design automated test cases according to scenarios and debug automated test scripts, with complete, clear and highly executable logical judgements
• Design performance test cases according to software performance requirements, and debug performance test scripts, with reasonable parameter and judgement settings to fully meet concurrent testing requirements
• Analyze interface input parameters, design interface test cases, and configure interface test scripts
• Design white-box test cases and test data based on unit logic
• Write test cases with complete content, fully ensuring case coverage, ease of execution, readability, and reusability.

The individual needs to know and understand:

• Commonly used performance testing, security testing, automated testing, code auditing and other tools
• The use of Linux and Windows operating systems, and common databases such as MySQL, Oracle, and SQLite
• Principles for evaluation and determination of test results
• The requirements for writing test records and defect reports
• The definition of defect severity and priority, and the causes of common problems
• Common problems and solutions in the testing process
• Software testing suspension and restart conditions
• The principles of determining regression testing scope
• Determination of the final test results of the software.

The individual shall be able to:

• Use testing tools to assist in functional testing, performance testing, interface testing, automated testing, white box testing, etc.
• Execute Linux and Windows commands and SQL statements to carry out testing when the use case contains relevant descriptions
• Accurately determine whether the test results have passed and whether the expected test purpose has been achieved
• Describe defects accurately, clearly, and concisely, avoiding ambiguity and redundancy
• Accurately determine the severity and priority of defects, make a preliminary assessment of the causes of defects, and provide repair suggestions in defect reports
• Solve common non-software defect problems during the testing process, such as network problems, environment compatibility problems, and script execution exceptions.
• Accurately determine when to terminate the test and when to restart the test
• Precisely determine the scope of defects and possible impact of defect repairs, determine the scope of regression testing, and create regression test suites
• Use the final test report to determine whether the test exit requirements are met.

The individual needs to know and understand:

• The purpose of test reports
• The structure of test reports
• The requirements for writing test report opinions and explanation
• The composition of the delivery documents
• Requirements for delivery of test reports
• The importance of summarizing the inductive testing experience and accumulating knowledge.

The individual shall be able to:

• Prepare test reports with complete content, accurate description, detailed data and clear conclusions
• Analyze and interpret test data, evaluate the overall quality of the software and the quality of each feature, and provide suggestions on discovered defects and subsequent optimization directions
• Review, archive and deliver all test process documents
• Deliver test reports while meeting customer requirements and confidentiality requirements
• Summarise Test Project experience and archive test assets and knowledge.