Hybrid work: 3 days in the office at (office location address) and 2 days remote from home office within Ontario; 

 

Responsibilities

Provides advice on the testing strategy, test plans, the selection of testing tools, and the identification of resources required for testing. Plans and organizes testing efforts for large systems in Graphical User Interface (GUI) and non-Graphical User Interface (GUI) environments, including the execution of systems integration tests, specialized tests, and user acceptance testing (e.g., stress tests).

The Quality Assurance Specialist is responsible for the development of test plans, test scripts and test cases and executing these against the various components. The tester will work with the testing lead and IT lead of each project as well as the project team members in the analysis, design, development, implementation and ongoing support of the required systems.

 

 

Responsibilities/Assignment Deliverables:

 

• Strong background in, and at least 3+ years of working in QA automation using Selenium or similar tool
• Compose manual and automated test scripts for new functionality
• Knowledge of Agile SCRUM preferred.
• Thorough understanding of SDLC, specifically automated QA processes in agile development environments
• Building test infrastructures using containerization technologies such as Docker and working within continuous delivery / continuous release pipeline processes
• Participate in business requirement review and walk through meetings;
• Collaborate with the Ministry to develop a Test Strategy and Plan for the pilot implementation
• Provide feedback to Drive Clean Management regarding the completeness and quality of the proposed vendor plan to execute
• Functional testing;
• Application integration (links, connections, security transactions between functions and main modules);
• System testing (end-to-end testing);
• Regression testing;
• User Acceptance testing;
• Execute UAT test cases and document the results
• Record application defects reported in the Cluster’s defect reporting tool – Azure
• Coordinate and facilitate regular defect review meeting with stakeholders
• Provide defect status reports throughout the testing cycles
• Participate in regular project team meeting and provide status and update as required;
• Provide weekly report confirming status of assigned tasks

 

The selected Testing/QA Specialist will be expected to ensure that the proposed Test

Strategy / Test plans include the following correction procedure.

1. Prioritize problems based on severity level definitions;

2. Identify problems, isolate them and document as defect;

3. Regression test for resolved defects

 

The selected Testing/QA Specialist will be expected to ensure that the proposed Test

Strategy / Test plans includes the following:

• Functional testing:
  • Component level testing;
  • Low level (test cases, GUI, check lists);
  • Functional (test existing functions, sub-functions and their objects);
  • Non-functional (boundary conditions- “login” and “password” windows, security issues);

and,

• Data and Database Integrity Testing
  • The databases and the database processes should be tested as separate systems within the test plan. These systems should be tested without the application (as the interface to the data).
• System Testing
  • System testing should focus on any target requirements that can be traced directly to use cases (or business functions), and business rules. The goals of these tests are to verify proper data acceptance, processing, and retrieval, and the appropriate implementation of the business rules.
• Load Testing
  • Load testing measures subject the system-under-test to varying workloads to evaluate the systems ability to continue to function properly under these different workloads. The goal of load testing is to determine and ensure that the system functions properly beyond the expected maximum workload. Additionally, load testing evaluates the performance characteristics (response times, transaction rates, and other time sensitive issues).
• Security and Access Control Testing
• Experience in doing AODA testing for WebUI and Documents
• Security and access control testing focus on two key areas of security:
• Application security, including access to the data or business functions, and system security, including logging into / remote access to the application
  • Application security which ensures that, based upon the desired security, users are restricted to specific functions or are limited in the data that is available to them. For example, everyone may be permitted to enter data and create new accounts, but only managers can delete them. If there is security at the data level, testing ensures that ‘user “type” one’ can see all customer information, including financial data, however, ‘user “type” two’ only sees the demographic data for the same ministry. System security ensures that only those users granted access to the system are capable of accessing the application and only through the appropriate gateways.

 

• Configuration Testing
  • Configuration testing verifies operation of the software on different software and hardware configurations. In most production environments, the particular hardware specifications for the Client workstations, network connections and database servers vary. Client workstations may have different software loaded (e.g. applications, rivers, etc.) and at any one time many different combinations may be active and using different resources.