Software testing
Software testing involves strategies and techniques to ensure quality. Learners contribute to the test process for a software solution.
Assessment criteria
Topic Overview
The City & Guilds Level 2 Diploma in ICT Systems Support provides a comprehensive foundation for students aspiring to become IT support technicians. This qualification covers essential skills such as installing and configuring hardware and software, maintaining computer networks, and providing user support. It is designed to prepare learners for entry-level roles in IT support or for further study in more advanced ICT qualifications.
Students will explore topics including computer hardware components, operating systems, networking fundamentals, security best practices, and troubleshooting methodologies. The course emphasizes practical, hands-on experience, ensuring that learners can apply theoretical knowledge to real-world scenarios. This diploma is recognized by employers and educational institutions, making it a valuable stepping stone into the ICT industry.
In the wider context of computer science, this diploma bridges the gap between basic digital literacy and specialized technical roles. It equips students with the problem-solving and communication skills needed to support end-users effectively. By understanding how systems work and how to maintain them, students gain a solid foundation for careers in IT support, network administration, or cybersecurity.
Key Concepts
Core ideas you must understand for this topic
- →Hardware components: Understanding the roles of CPU, RAM, storage devices, motherboards, and peripherals, and how they interact within a computer system.
- →Operating systems: Installing, configuring, and troubleshooting Windows and Linux OS, including file management, user accounts, and system utilities.
- →Networking fundamentals: Concepts such as IP addressing, subnetting, DNS, DHCP, and setting up local area networks (LANs) with switches and routers.
- →Security principles: Implementing antivirus software, firewalls, user authentication, and data backup strategies to protect systems from threats.
- →Troubleshooting methodology: Using a systematic approach (identify, analyze, test, resolve, document) to diagnose and fix hardware, software, and network issues.
Learning Objectives
What you need to know and understand
- Know about testing strategies and techniques, Contribute to a test process for a software solution
- Describe the purpose and importance of software testing in the development lifecycle.
- Explain different testing strategies (e.g., black-box, white-box, unit, integration, system, acceptance) and their appropriate use.
- Apply appropriate testing techniques to design test cases for a given software solution.
- Contribute to the creation of a test plan, including test objectives, scope, and resources.
- Execute test cases and record results accurately.
- Report defects clearly and concisely, including steps to reproduce and severity.
- Evaluate the effectiveness of testing activities and suggest improvements.
- Know about testing strategies and techniques, Contribute to a test process for a software solution
- Know about testing strategies and techniques, Contribute to a test process for a software solution
- Know about testing strategies and techniques, Contribute to a test process for a software solution
Assessment Criteria
Key criteria assessors look for in your portfolio
- Describe testing strategies and techniques.
- Contribute to a test process effectively.
- Document test results accurately.
- Award credit for demonstrating understanding of the purpose of testing, including defect detection and quality assurance.
- Award credit for correctly distinguishing between different testing strategies and explaining when each is used.
- Award credit for producing test cases that cover both positive and negative scenarios.
- Award credit for contributing to a test plan that includes clear objectives, scope, and resource considerations.
- Award credit for executing tests methodically and recording results in a structured format.
- Award credit for writing defect reports that include all necessary information: title, description, steps to reproduce, expected vs actual result, and severity.
- Award credit for reflecting on the test process and identifying potential improvements.
- Describe different testing strategies (e.g., black box, white box).
- Explain the purpose of testing at different stages.
- Create test cases based on requirements.
- Execute tests and record results accurately.
- Describe different testing strategies (e.g., unit, integration, system).
- Explain techniques like black-box and white-box testing.
- Contribute to a test process by creating test cases and reporting defects.
- Understand the importance of test documentation and traceability.
- Describes different testing strategies (e.g., black-box, white-box, regression).
- Creates test cases based on requirements or user stories.
- Executes tests and records results accurately.
- Reports defects clearly with steps to reproduce.
Assessment Guidance
Guidance for achieving higher grades
- 💡Know different testing levels (unit, integration, system).
- 💡Use examples from real projects.
- 💡Follow a structured test process.
- 💡Use real-world examples to illustrate testing concepts, such as a login system or e-commerce checkout.
- 💡When contributing to a test process, always follow a structured approach: plan, design, execute, and report.
- 💡Remember that testing is not just about finding bugs but also about verifying that the software meets requirements.
- 💡In assessments, clearly link your testing activities to the overall software development lifecycle.
- 💡Use a structured test plan for practical tasks.
- 💡Prioritise tests based on risk.
- 💡Learn common testing terminology.
- 💡Learn the V-model and its relationship to testing phases.
- 💡Practice writing clear, concise defect reports.
- 💡Understand the difference between static and dynamic testing.
- 💡Use a sample application to demonstrate test case creation.
- 💡Explain the purpose of each testing level (unit, integration, system).
- 💡Show how testing fits into the software development lifecycle.
- 💡When answering questions about troubleshooting, always mention a clear, step-by-step process. Start with identifying the problem, then isolating the cause, testing solutions, and finally documenting the outcome. This structured approach earns higher marks.
- 💡For networking questions, draw diagrams to illustrate your understanding of how devices connect. Label IP addresses, subnet masks, and default gateways. Visual aids can clarify complex concepts and demonstrate practical knowledge.
- 💡In hardware questions, be specific about component specifications (e.g., 'DDR4 RAM' rather than just 'RAM'). Mentioning relevant details like capacity, speed, and compatibility shows depth of understanding.
Common Mistakes
Common errors to avoid in your coursework
- Confusing testing strategies with techniques.
- Skipping test documentation.
- Not considering edge cases.
- Confusing testing strategies with testing levels (e.g., thinking unit testing is a strategy rather than a level).
- Writing test cases that only cover expected inputs and not edge cases or invalid inputs.
- Failing to document test results properly, making it difficult to track defects.
- Reporting defects without sufficient detail, such as missing steps to reproduce or ignoring severity levels.
- Testing only happy paths, ignoring edge cases.
- Not documenting test results properly.
- Confusing verification with validation.
- Confusing verification with validation.
- Writing test cases that are too vague or too detailed.
- Not prioritising tests based on risk.
- Testing only happy paths and ignoring edge cases.
- Poor defect reporting lacking environment details or steps.
- Confusing verification with validation.
- Misconception: 'More RAM always makes a computer faster.' Correction: While adding RAM can improve performance if the system is memory-constrained, excessive RAM beyond what applications require does not provide additional speed. The benefit depends on the workload.
- Misconception: 'Antivirus software alone guarantees complete security.' Correction: Antivirus is just one layer of security. Users must also practice safe browsing, keep software updated, use strong passwords, and enable firewalls to reduce risk.
- Misconception: 'IP addresses are permanent and never change.' Correction: IP addresses can be dynamic (assigned by DHCP) or static. Many devices receive a new IP address each time they connect to a network, unless configured with a static IP.
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for CITY & GUILDS LIMITED Software testing
Every vocational unit is marked against named criteria rather than an exam percentage. Your tutor's brief lists the exact codes for this unit — here is what each band is asking you to do.
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic digital literacy: Familiarity with using a computer, managing files, and browsing the internet.
- •Fundamental mathematics: Understanding of binary numbers, basic arithmetic, and logical reasoning for networking and troubleshooting.
- •Communication skills: Ability to explain technical concepts clearly, as user support requires effective interaction with non-technical users.
Coursework AI Review
Paste your assignment brief and check your draft against its P/M/D criteria
Key Terminology
Essential terms to know
- Know about testing strategies and techniques, Contribute to a test process for a software solution
- Testing strategies and techniques
- Test planning and documentation
- Defect identification and reporting
- Role of tester in test process
- Quality assurance and control
- Know about testing strategies and techniques, Contribute to a test process for a software solution
- Know about testing strategies and techniques, Contribute to a test process for a software solution
- Know about testing strategies and techniques, Contribute to a test process for a software solution
Ready to learn?
AI-powered learning tailored to this unit