Ontario Skills Passport
Layout structure
Header structure
Display Noc
OSP Occupational Profile

OSP Occupational Profile

Print Occupational Profile

Display page browsing back option list
Display page browsing back option list <<Back
Display Noc Details
NOC Code: NOC Code: 2283 Occupation: Systems Testing Technicians
Occupation Description: Occupation Description:
Systems testing technicians execute test plans to evaluate the performance of software applications and information and telecommunications systems. They are employed in information technology units throughout the private and public sector. Systems testing technicians execute test plans to evaluate the performance of software applications and information and telecommunications systems. They are employed in information technology units throughout the private and public sector.

  • Click on any of the Essential Skills to view sample workplace tasks for this occupation.
  • Scroll down the page to get information on career planning, education and training, and employment and volunteer opportunities.

Table will display the Skill Level for the Noc specified
Essential Skills Essential Skills Levels
Reading Reading 1 2 3 4
Writing Writing 1 2 3 4
Document Use Document Use 1 2 3
Digital Technology Digital Technology 1 2 3 4 5
Oral Communication Oral Communication 1 2 3
Money Math Money Math 1 2
Scheduling or Budgeting and Accounting Scheduling or Budgeting and Accounting 1 2 3
Measurement and Calculation Measurement and Calculation 1 2
Data Analysis Data Analysis 1 2 3
Numerical Estimation Numerical Estimation 1
Job Task Planning and Organizing Job Task Planning and Organizing 1 2 3
Decision Making Decision Making 1 2 3
Problem Solving Problem Solving 1 2 3
Finding Information Finding Information 1 2 3
Critical Thinking Critical Thinking 1 2 3

  • The skill levels represented in the above chart illustrate the full range of sample tasks performed by experienced workers and not individuals preparing for or entering this occupation for the first time.
  • Note that some occupational profiles do not include all Numeracy and Thinking Essential Skills.

If you would like to print a copy of the chart and sample tasks, click on the "Print Occupational Profile" button at the top of the page.

  • Read short error messages and alerts, e.g. read short error log messages in the software applications that were tested. (1)
  • Read email and memos from co-workers, e.g. read email messages from co-workers to learn about preliminary test results and memos from managers to learn of changes to software launch dates. (2)
  • Read text entries in forms, e.g. read test instructions and corrective actions required in test case forms. (2)
  • Read articles, reviews and editorials in trade publications and forums, e.g. read expert reviews of domain-specific software products and new operating systems in trade publications, such as Computer Weekly and PC Magazine. (3)
  • Read software specifications, release logs and test reports, e.g. read developers' specifications of new software modules to learn about functions, design considerations and architecture and study release logs to identify the objectives, system compatibilities, defects solved and build histories of new software releases. (4)
  • Read policies and methodologies, e.g. testing technicians carrying out automated testing read functional test methodologies to learn about designing and constructing automated test suites. (4)
  • Read manuals, e.g. read computer hardware and software manuals to learn installation and configuration procedures. (4)
Back to Top

  • Write short notes and reminders, e.g. write descriptions of tasks in testing logs and reminders to co-workers about upcoming tests. (1)
  • Write email and memos, e.g. write email to respond to co-workers' questions and memos to explain testing results to development team members. (2)
  • Write rules and procedures, e.g. write sequenced instructions to co-workers to explain how to install computer hardware and software. (3)
  • Write reports, e.g. write test summary reports to describe test design methodologies, tests performed, defects found and fixed, and recommendations. (4)
Back to Top

Document Use
  • Locate data on labels, e.g. view equipment labels to identify ports, connectors and switches for computer hardware and peripherals. (1)
  • Enter data into lists, tables and schedules, e.g. enter data, such as times, dates, quantities and frequencies, into test schedules. (2)
  • Locate data in lists, tables and schedules, e.g. locate hardware devices in lists of test requirements and start and finish dates for specific tests in schedules. (2)
  • Locate data in entry forms, e.g. locate test case identifiers, categories, specifications, requirements, steps and expected results in test case forms. (2)
  • Locate data and identify trends in graphs, e.g. software test coordinators locate test result data in line graphs. (2)
  • Locate and interpret data in schematic drawings, e.g. study class and class interaction diagrams to learn about networks and their constituent parts. (3)
  • Locate data in charts, e.g. test coordinators locate start and finish dates, project objectives and names of developers for the development of specific software modules on Gantt charts. (3)
  • Complete forms, such as test plans, test scripts, test progress logs, defect tracking forms and build release forms, e.g. enter titles, dates, build numbers, descriptions, status and priorities of defects into tracking forms. (3)
Back to Top

Digital Technology
  • Use communication software to manage job tasks and schedule meetings. (2)
  • Use communication software to exchange email and attachments with co-workers, colleagues, network users and suppliers. (2)
  • Use graphics software to edit screenshots and photographs presented in user manuals. (2)
  • Use Internet browsers to access online trade publications to stay current on industry trends and practices. (2)
  • Use the Internet to access blogs and web forums where you seek and offer troubleshooting and other technical advice. (2)
  • Use search engines to obtain information on error messages, testing practices and software applications. (2)
  • Use hardware and system skills to set up and connect computers and peripherals for tests. (2)
  • Use the Internet to test web-based applications. (3)
  • Use spreadsheet software to collect, analyze and graph test data. (3)
  • Use the Internet to download release logs, software manuals and applications from Intranet servers and suppliers' websites. (3)
  • Use advanced features of word processing programs to write and format memos, test cases, procedures, methodologies and reports. Create tables and indexes and import screen shots, spreadsheets and graphics. (3)
  • Use hardware and system skills to install and configure various test management applications, such as defect tracking software and revision control applications. (4)
  • Use hardware and system skills to install and configure operating systems to test the compatibility of software applications in various environments. (4)
  • Use automated testing tools, such as Rational Suite and Quick Test Professional, to design tests and implement testing systems. (5)
  • Use programming, software design and development skills to do programming, software design and development, such as writing batch files to execute automated test suites. (5)
  • Use programming, software design and development skills to install and configure software applications under development, write test scripts and cases and run tests in order to evaluate the performance of these applications. (5)
Back to Top

Oral Communication
  • Speak with suppliers, e.g. talk with suppliers to determine the delivery date of supplies and materials. (1)
  • Discuss technical information with co-workers, e.g. speak with co-workers about adaptations to critical test cases and defects in software applications. (2)
  • Make presentations, e.g. make presentations to supervisors and managers to explain the principles, requirements, advantages and disadvantages of automated testing of software applications. (3)
  • Exchange technical information with help desk technicians, e.g. speak to suppliers' support technicians to troubleshoot difficulties in integrating new versions of software applications. (3)
Back to Top

Money Math
  • Calculate amounts for expense claims. Add amounts for software and supplies purchased and calculate charges for the use of personal vehicles at per kilometre rates. (2)
Back to Top

Scheduling or Budgeting and Accounting
  • Create and monitor testing schedules. Monitor testing progress on many software projects and change test schedules to adapt to delays and revisions in software development plans. (3)
Back to Top

Measurement and Calculation
  • Verify calculations made by software applications, e.g. application testers verify printing costs calculated by print tracking applications. Check that the printing costs calculated automatically are equal to the number of sheets printed multiplied by the appropriate per sheet prices. (2)
Back to Top

Data Analysis
  • Compare test data and equipment readings to specifications, e.g. compare transaction numbers and dates generated by software applications during tests to expected numbers and dates. (1)
  • Collect and analyze test data to identify software malfunctions and to assess the effectiveness of test methods and processes, e.g. count numbers of critical defects in software applications and monitor these numbers through test cycles to draw conclusions about software reliability. (3)
Back to Top

Numerical Estimation
  • Estimate time to complete a job task using past experience as a guide, e.g. estimate times to complete functional tests, usability tests and performance tests. (1)
Back to Top

Job Task Planning and Organizing
  • Systems testing technicians plan and organize their daily tasks to give priority to test plans prepared by supervisors. They may adapt and revise job task plans as software modules and solutions to program defects are delivered by software developers. They may experience conflicting demands on their time as software release dates approach. (3)
Back to Top

Decision Making
  • Choose test cases to uncover defects in software and information and telecommunications systems, e.g. testers choose test cases and sequences in order to meet specifications, test objectives and time constraints. (2)
  • Select the testing software to design, implement and test software, applications, products and systems. Consider the scope of projects, testing specifications, timelines and budgets. (3)
  • Choose test processes, plans and methodologies, e.g. software test coordinators choose how to test software to affirm its usability, reliability, compatibility and performance. (3)
Back to Top

Problem Solving
  • Deadlines cannot be met due to heavy workloads and projects which take longer than anticipated to complete. Speak with supervisors about the delays, enlist the help of co-workers and work overtime to complete high priority work. (2)
  • Find that computer systems malfunction and crash during software tests. Attempt to diagnose the causes of breakdowns and carry out repairs. Call technical support analysts to repair malfunctioning systems. (2)
  • Encounter poor coordination between software development and testing work, e.g. development teams have not fixed software defects in time for critical testing. Speak with development team leaders about the needed fixes and revise testing schedules as required. Propose improvements in communication between development and testing teams. (3)
Back to Top

Finding Information
  • Find information about testing tools and practices by reading manuals, user forums and trade publications and by speaking with co-workers and help desk technicians. (3)
  • Find information about the terminologies and concepts specific to the domains of software programs. Read development specifications and background reports, conduct Internet searches and consult co-workers to learn about the needs of users who will use the software programs tested. (3)
Back to Top

Critical Thinking
  • Assess the effectiveness of testing processes. Monitor test results and tracking reports to identify delays and unresolved defects. Review customers' questions and complaints to identify important software defects that were not detected during testing. (3)
  • Evaluate the usability of documentation for software applications and systems, e.g. testing technicians proofread installation manuals to identify errors in spelling and grammar and confirm that accompanying screenshots and graphics are accurate and effective. (3)
  • Evaluate the quality and performance of software applications and systems. Identify important quality criteria, such as speed, capacity, security and reliability. Set benchmarks that reflect customers' requirements and developers' specifications. Analyze test results and make ongoing recommendations to developers about necessary changes to programming code and software functions. (3)
Back to Top