Quality Assurance 6000

All candidates, please note this role is fully onsite

Responsibilities:
Familiar with Quality Assurance Methodologies and Best Practices.
Experience with Manual Functional and SIT Testing using existing Test Cases/Scripts.
Is able to create Test Cases/Scripts from predefined user Requirements.
Must be able to Open, Document Defects and Retesting Defects using Defect Management Tools as well as provide Testing Status updates to Test Leads. Is familiar with Test strategy and Test Plans. Understands and Identifies Test Data requirements.

Familiar with large system Graphical User Interface (GUI) and non-Graphical User Interface (GUI) environments, including the execution of systems integration tests, specialized tests if required and user acceptance testing if required(e.g., stress tests). The Junior System Tester/Quality Assurance Specialist is able to follow test plans, test scripts and test cases and execute 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 General


Skills:

Experience in planning, organizing and providing status of testing.



Desirable Skills:
Knowledge and understanding of Accessibility for Ontarians with Disability Act (AODA) and related regulations and standards

Experience planning and organizing testing efforts for both large and small system
Experience coding automated test scripts to produce sets of automated test cases Experience testing Commercial Off-the Shelf Applications (COTS)

Experience and Skill Set Requirements:

Quality assurance (QA), as defined in the RIDE-TI Testing Strategy, is the systematic process of determining whether IT solutions that have been developed and unit tested by the developers meets the specified requirements prior to delivering it to the business for user acceptance testing.

QA will ensure the solution operates as expected based on design documents; mitigates any technical issues that could potentially arise; ensures the solution is error free and confirms the quality of the solution meets CAC standards and expectations.

The RIDE-TI QA includes the following types of testing:


System Testing:
System testing is conducted on a complete, integrated system to determine that the system functions the way it should as a whole and to evaluate the system and #x27;s compliance with its specified requirements. System testing input is all the and quot;integrated and quot; software components that have successfully passed unit testing and the software system itself integrated with any applicable hardware system(s). System testing is comprehensive and includes testing of all components. The intent of this testing is to identify and resolve as many system defects as possible before making the system available to the business users for testing

Integration Testing:
Integration testing is the software testing in which individual software components are combined and tested collectively. During system/integration testing, the separate units/modules will be tested together to ensure they work together to provide the required results as per the specified requirements.

AODA Testing:
The Accessibility for Ontarians with Disabilities Act (AODA) is the compliance testing required to meet the Government of Ontario and #x27;s Accessibility for Ontarians with Disabilities Act. Ministries and clusters have been responsible for testing their new website and web products and ensuring that they meet established accessibility standards as per the AODA since 2012 and are accountable for ensuring that their websites and web content are compliant with legislation, including accessibility legislation such as the Ontarians with Disabilities Act (ODA) and the Accessibility for Ontarians with Disabilities Act (AODA).

Regression Testing:
Regression testing is the process of testing changes to computer programs/applications to make sure that there is no impact to existing functionality. It verifies that changes to the solution do not negatively impact the unchanged functionality. Regression testing must be carried out where newly developed systems connect to existing systems to ensure nothing is changed in the existing functionalities of such systems

End-to-end Testing:
End-To-End testing simulates full production cycles to detect any inconsistencies between all the business processes involved in the implementation. It is used to test peripheral systems/applications that feed into our solution and receive feeds from our system, business requirements throughout the system and whether the flow of the system(s) from start to finish is behaving as expected. The purpose of performing end-to-end testing is to identify a smooth transition for the end user as the data flows through the system.

Successful candidate should have demonstrated experience:

• Writing and documenting test scenarios and test scripts
• Completing all preparatory activities including test materials
• Testing using imaging and data capture solutions
• Documenting test results and reporting progress
• Creating, updating and monitoring defects to support defect triage and resolution
• Updating business requirements documentation and participating in design sessions
• Working within OPS

Evaluation Criteria:

- QA skills and experience - 70%
- Soft skills / communication skills - 20%
- OPS experience - 10%