Testing ICT Systems
CITY & GUILDS LIMITED
Vocational
This topic covers planning and producing standard testing procedures, selecting tests, determining expected results, managing consequences of testing, and applying tests to analyse results.
15
Learning Outcomes
33
Assessment Guidance
33
Key Skills
15
Key Terms
43
Assessment Criteria
Assessment criteria
City & Guilds Level 4 Diploma For ICT Professionals (Systems and Principles)
City & Guilds Level 3 Certificate in ICT Systems and Principles
City & Guilds Level 2 Diploma in ICT Systems Support
City & Guilds Level 3 Diploma in ICT Systems Support
City & Guilds Level 3 Diploma in ICT Systems and Principles for IT Professionals
City & Guilds Level 2 Diploma in ICT Systems and Principles for IT Professionals
City & Guilds Level 2 Certificate in ICT Systems Support
City & Guilds Level 2 Award in ICT Systems and Principles
City & Guilds Level 2 Diploma in ICT Professional Competence
City & Guilds Level 3 Diploma in ICT Professional Competence
Topic Overview
The City & Guilds Level 3 Diploma in ICT Systems Support is a vocational qualification designed to equip students with the practical skills and theoretical knowledge needed to support and maintain ICT systems in a professional environment. This diploma covers a broad range of topics including hardware installation, software configuration, network management, and user support. It is ideal for those aiming to become IT support technicians, helpdesk analysts, or network administrators, as it provides hands-on experience with real-world scenarios and industry-standard tools.
Throughout the course, students will learn how to diagnose and resolve technical issues, manage system security, and implement effective backup and recovery strategies. The qualification emphasizes problem-solving, communication, and customer service skills, which are essential for providing high-quality support in any organization. By the end of the diploma, students will be prepared for entry-level roles in ICT support or further study in areas such as networking or cybersecurity.
This diploma is part of the wider ICT professional framework and aligns with industry standards such as CompTIA A+ and ITIL. It is recognized by employers across various sectors, making it a valuable stepping stone for a career in IT. The course also develops transferable skills like teamwork and time management, which are crucial for success in the workplace.
Key Concepts
Core ideas you must understand for this topic
- →Hardware and Software Installation: Understanding how to install, configure, and maintain computer hardware components (e.g., CPUs, RAM, hard drives) and software applications, including operating systems and drivers.
- →Network Fundamentals: Knowledge of network topologies, protocols (e.g., TCP/IP), IP addressing, and basic network devices like routers and switches. This includes setting up and troubleshooting local area networks (LANs).
- →User Support and Troubleshooting: Developing systematic approaches to diagnose and resolve common ICT issues, using tools like event viewers, command-line utilities, and remote desktop software. Effective communication with end-users is key.
- →Security and Data Protection: Implementing security measures such as antivirus software, firewalls, user authentication, and encryption. Understanding backup strategies and disaster recovery to protect data integrity.
- →System Maintenance and Documentation: Performing routine maintenance tasks like disk cleanup, defragmentation, and software updates. Creating clear documentation for configurations, procedures, and troubleshooting steps.
Learning Objectives
What you need to know and understand
- Plan and produce standard testing procedures, Select tests and determine expected results, Identify and manage consequences of testing, Apply tests and analyse results
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Perform systematic diagnostic tests on PC systems using industry-standard tools
- Apply appropriate test procedures to verify the functionality of common peripherals
- Interpret diagnostic results and error codes to pinpoint faulty hardware components
- Implement approved remedial actions to resolve identified hardware and software faults
- Document test procedures, outcomes, and repairs in line with organisational requirements
- Evaluate the effectiveness of applied fixes to confirm full system restoration
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Know technical information about a range of products, testing procedures and associated activities, equipment to be used and the reasons for the test, Carry out routine testing and assist in other testing
- Know technical information about a range of products, testing procedures and associated activities, equipment to be used and the reasons for the test, Carry out routine testing and assist in other testing
Assessment Criteria
Key criteria assessors look for in your portfolio
- Plans and produces standard testing procedures for ICT systems.
- Selects appropriate tests and determines expected results.
- Identifies and manages consequences of testing (e.g., data loss, downtime).
- Applies tests and analyses results to verify system performance.
- Uses diagnostic tools and test procedures correctly.
- Applies standard tests to PC systems and peripherals.
- Interprets test results to identify faulty components.
- Applies simple fixes such as reseating components or replacing parts.
- Award credit for demonstrating the use of industry-standard diagnostic tools (e.g., POST cards, multimeters, or software utilities) in a logical sequence.
- Expect learners to follow a structured test procedure, documenting each step and recording baseline measurements before and after interventions.
- Require clear interpretation of test results, including the ability to isolate a faulty component (e.g., RAM, HDD, PSU) and justify the diagnosis.
- Credit application of a simple fix, such as reseating a component, replacing a peripheral, or adjusting BIOS settings, with verification that the issue is resolved.
- Use typical diagnostic tools (e.g., multimeter, software diagnostics).
- Apply standard test procedures to PC systems and peripherals.
- Interpret test results to identify faulty components.
- Apply simple fixes (e.g., reseating RAM, replacing cables).
- Describe typical diagnostic and test procedures.
- Apply standard test procedures to PC systems and peripherals.
- Interpret test results to identify faulty components.
- Explain simple fixes for common faults.
- Uses appropriate diagnostic software and hardware tools.
- Applies standard test procedures to PC systems and peripherals.
- Interprets test results to pinpoint faulty components.
- Performs simple fixes such as replacing RAM or hard drives.
- Award credit for correctly following a diagnostic flowchart or manufacturer guidelines
- Evidence of using appropriate testing tools (e.g., multimeter, loopback plugs, diagnostic software)
- Accurate interpretation of POST beep codes, LED indicators, or error messages
- Clear documentation of test results, fault diagnosis, and actions taken
- Demonstration of safe working practices, including electrostatic discharge prevention
- Logical elimination of potential causes before concluding component failure
- Use appropriate diagnostic tools and test procedures.
- Apply standard tests to PC systems and peripherals correctly.
- Interpret test results to identify faulty components.
- Apply simple fixes such as reseating RAM or replacing cables.
- Interpret technical information about ICT products.
- Select appropriate testing procedures for given systems.
- Carry out routine testing accurately and safely.
- Document test results and report faults.
- Describe different types of testing (unit, integration, system, acceptance).
- Explain the purpose of a test plan and test cases.
- Identify common testing tools and their uses.
- Carry out a basic test and record results accurately.
- State the importance of regression testing.
Assessment Guidance
Guidance for achieving higher grades
- 💡Use a structured approach like the testing lifecycle.
- 💡Include both functional and non-functional tests.
- 💡Always record actual vs. expected results.
- 💡Learn common POST error codes and beep sequences.
- 💡Practice using multimeters and loopback plugs.
- 💡Always follow ESD precautions when handling components.
- 💡Always structure your answer around a ‘plan-do-check’ cycle: describe the test procedure, the expected vs. actual results, and the fix applied.
- 💡In practical assessments, narrate your actions to the assessor, explaining why you chose a specific test and how you are interpreting real-time results.
- 💡Memorise common fault patterns for typical components (e.g., no display with fans spinning often points to RAM or GPU) to speed up diagnosis.
- 💡When documenting fixes, include both the technical action (e.g., ‘replaced SATA cable’) and the user impact (e.g., ‘restored data access’) to show vocational awareness.
- 💡Start with the simplest possible cause.
- 💡Document each test and result.
- 💡Use manufacturer guidelines for diagnostics.
- 💡Follow a systematic troubleshooting approach.
- 💡Use diagnostic tools like multimeters and software utilities.
- 💡Always check connections and power supply first.
- 💡Follow a systematic troubleshooting approach (e.g., divide and conquer).
- 💡Keep a reference of common error codes and their meanings.
- 💡Practice swapping components to isolate faults.
- 💡Always state the rationale for chosen diagnostic steps in written assignments
- 💡In practical assessments, systematically eliminate potential causes starting from the most likely
- 💡Familiarise yourself with common error codes and diagnostic software tools before the exam
- 💡Use precise terminology when describing faults and repairs to demonstrate technical competence
- 💡Double-check that all peripherals are compatible and correctly configured before testing
- 💡Follow a logical troubleshooting sequence.
- 💡Document each step and result for clarity.
- 💡Know common error codes and their meanings.
- 💡Know common testing tools like multimeters and cable testers.
- 💡Understand the difference between functional and performance testing.
- 💡Always record results for traceability.
- 💡Use industry-standard terminology (e.g., bug, defect).
- 💡Show understanding of the testing lifecycle.
- 💡Emphasise the role of testing in quality assurance.
- 💡When answering questions about troubleshooting, always structure your response using a logical process: identify the problem, gather information, consider possible causes, test solutions, and document the outcome. This demonstrates a methodical approach that examiners reward.
- 💡For network-related questions, be precise with terminology. For example, distinguish between a hub, switch, and router, and explain their OSI model layers. Use diagrams where appropriate to show your understanding of network topologies.
- 💡In security questions, emphasize the principle of 'defense in depth' – using multiple layers of security (e.g., firewalls, antivirus, access controls) rather than relying on a single measure. This shows a comprehensive understanding of security best practices.
Common Mistakes
Common errors to avoid in your coursework
- Not documenting test procedures clearly.
- Failing to consider the impact of testing on live systems.
- Overlooking regression testing after changes.
- Skipping basic checks like cable connections.
- Misinterpreting error codes without research.
- Not documenting test results for future reference.
- Jumping to conclusions without completing a full diagnostic cycle, often leading to unnecessary replacement of working parts.
- Confusing symptoms with root causes, e.g., replacing a power supply when the real issue is a faulty power button cable.
- Neglecting to check basic factors first, such as loose cables, power connections, or compatibility before diving into complex tests.
- Misinterpreting beep codes or LED indicators due to reliance on memory rather than consulting motherboard or device manuals.
- Not following a logical troubleshooting sequence.
- Misinterpreting error codes or test results.
- Attempting repairs without proper ESD precautions.
- Misdiagnosing faults due to incomplete testing.
- Overlooking software issues when hardware appears faulty.
- Failing to document test results.
- Misinterpreting error codes or test results.
- Skipping basic checks (e.g., cables, power) before deeper diagnostics.
- Not documenting test procedures and outcomes.
- Confusing symptoms of power supply failure with motherboard issues
- Neglecting to verify cable connections before concluding component failure
- Applying fixes without proper ESD precautions, risking further damage
- Misinterpreting software errors as hardware faults without ruling out driver issues
- Skipping basic checks (e.g., power, connectivity) and moving directly to complex diagnostics
- Skipping steps in the test procedure.
- Misinterpreting error codes or test results.
- Attempting complex repairs beyond the scope of simple fixes.
- Not following test plans or procedures.
- Overlooking environmental factors affecting performance.
- Failing to back up data before testing.
- Testing only 'happy path' scenarios.
- Inadequate documentation of test results.
- Skipping test planning and going straight to execution.
- Misconception: ICT support is just about fixing hardware. Correction: While hardware repair is part of it, the role involves much more, including software troubleshooting, network configuration, user training, and security management. A good support technician must have a broad skill set.
- Misconception: You need to know everything about computers to succeed. Correction: No one knows everything. The key is knowing how to find information quickly, using resources like knowledge bases, forums, and vendor documentation. Problem-solving skills are more important than memorizing facts.
- Misconception: Backups are optional if you have antivirus software. Correction: Antivirus protects against malware, but it doesn't prevent hardware failure, accidental deletion, or natural disasters. Regular backups are essential for data recovery in any scenario.
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 Testing ICT Systems
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.
Pass (P)
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Merit (M)
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Distinction (D)
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic understanding of computer hardware components (e.g., CPU, RAM, hard drive) and their functions.
- •Familiarity with common operating systems like Windows and basic file management.
- •Elementary knowledge of networking concepts such as IP addresses and the internet.
Coursework AI Review
Paste your assignment brief and check your draft against its P/M/D criteria
Key Terminology
Essential terms to know
- Plan and produce standard testing procedures, Select tests and determine expected results, Identify and manage consequences of testing, Apply tests and analyse results
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Diagnostic methodologies
- Peripheral testing
- Fault identification
- Remedial actions
- Test documentation
- Health and safety in testing
- Use typical diagnostic and test procedures, Apply standard test procedures to PC systems and peripherals, Interpret test results to identify faulty components and apply simple fixes
- Know technical information about a range of products, testing procedures and associated activities, equipment to be used and the reasons for the test, Carry out routine testing and assist in other testing
- Know technical information about a range of products, testing procedures and associated activities, equipment to be used and the reasons for the test, Carry out routine testing and assist in other testing
Ready to learn?
AI-powered learning tailored to this unit