QA (Junior) 9758-2511

Oshawa - Canada

Monthly Salary: Not Disclosed

Posted on: 30+ days ago

Vacancies: 1 Vacancy

Job Summary

HM Note: This hybrid contract role is five (5) days in office. Candidates resumes must include first and last name.

Description

Responsibilities: and nbsp;

Good and nbsp;understanding and nbsp;of and nbsp;Quality and nbsp;Assurance and nbsp;Methodologies and nbsp;and and nbsp;Best and nbsp;Practices. and nbsp;
Experience and nbsp;with and nbsp;Manual and nbsp;Functional and nbsp;and and nbsp;SIT and nbsp;Testing and nbsp;using and nbsp;existing and nbsp;Test and nbsp;Cases/Scripts. and nbsp;Is and nbsp;able and nbsp;to and nbsp;create and nbsp;Test and nbsp;Cases/Scripts and nbsp;from and nbsp;predefined and nbsp;user and nbsp;Requirements. and nbsp;
Must and nbsp;be and nbsp;able and nbsp;to and nbsp;Open and nbsp;Document and nbsp;Defects and nbsp;and and nbsp;Retesting and nbsp;Defects and nbsp;using and nbsp;Defect and nbsp;Management and nbsp;Tools and nbsp;as and nbsp;well and nbsp;as and nbsp;provide and nbsp;Testing and nbsp;Status and nbsp;updates and nbsp;to and nbsp;Test and nbsp;Leads. and nbsp;
Is and nbsp;familiar and nbsp;with and nbsp;Test and nbsp;strategy and nbsp;and and nbsp;Test and nbsp;Plans. and nbsp;
Understands and nbsp;and and nbsp;Identifies and nbsp;Test and nbsp;Data and nbsp;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 Jr. System Tester/Quality Assurance Specialist is able to follow test plans test scripts and test cases and executing these against the various components
and nbsp;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 and nbsp;Skills: and nbsp;

Experience and nbsp;in and nbsp;planning and nbsp;organizing and nbsp;and and nbsp;providing and nbsp;status and nbsp;of and nbsp;testing. and nbsp;

Desirable and nbsp;Skills: and nbsp;

Knowledge and nbsp;and and nbsp;understanding and nbsp;of and nbsp;Accessibility and nbsp;for and nbsp;Ontarians and nbsp;with and nbsp;Disability and nbsp;Act and nbsp;(AODA) and nbsp;and and nbsp;related and nbsp;regulations and nbsp;and and nbsp;standards and nbsp;
Experience and nbsp;planning and nbsp;and and nbsp;organizing and nbsp;testing and nbsp;efforts and nbsp;for and nbsp;both and nbsp;large and nbsp;and and nbsp;small and nbsp;systems and nbsp;
Experience and nbsp;coding and nbsp;automated and nbsp;test and nbsp;scripts and nbsp;to and nbsp;produce and nbsp;sets and nbsp;of and nbsp;automated and nbsp;test and nbsp;cases and nbsp;
Experience and nbsp;testing and nbsp;Commercial and nbsp;Off-the and nbsp;Shelf and nbsp;Applications and nbsp;(COTS)

Skills

Experience and Skill Set Requirements

and nbsp;

Systems and nbsp;Testing/QA and nbsp;Specialized and nbsp;- and nbsp;Jr. and nbsp;details:

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 and nbsp;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 systems compliance with its specified requirements. System testing input is all the integrated 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

and nbsp;

Integration and nbsp;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.

and nbsp;

AODA and nbsp;Testing:
The Accessibility for Ontarians with Disabilities Act (AODA) is the compliance testing required to meet the Government of Ontarios 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).

and nbsp;

Regression and nbsp;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

and nbsp;

End-to-end and nbsp;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 and nbsp;candidate and nbsp;should and nbsp;have and nbsp;demonstrated and nbsp;experience:
Writing and nbsp;and and nbsp;documenting and nbsp;test and nbsp;scenarios and nbsp;and and nbsp;test and nbsp;scripts
Completing and nbsp;all and nbsp;preparatory and nbsp;activities and nbsp;including and nbsp;test and nbsp;materials
Testing and nbsp;using and nbsp;imaging and nbsp;and and nbsp;data and nbsp;capture and nbsp;solutions
Documenting and nbsp;test and nbsp;results and nbsp;and and nbsp;reporting and nbsp;progress
Creating and nbsp;updating and nbsp;and and nbsp;monitoring and nbsp;defects and nbsp;to and nbsp;support and nbsp;defect and nbsp;triage and nbsp;and and nbsp;resolution
Updating and nbsp;business and nbsp;requirements and nbsp;documentation and nbsp;and and nbsp;participating and nbsp;in and nbsp;design and nbsp;sessions
Experience and nbsp;in and nbsp;testing and nbsp;COTS and nbsp;solution
Experience and nbsp;in and nbsp;conducting and nbsp;data and nbsp;mapping and nbsp;exercise and nbsp;and and nbsp;validation and nbsp;testing
Experience and nbsp;of and nbsp;working and nbsp;within and nbsp;OPS
Experience working with Azure DevOps

Evaluation and nbsp;Criteria:

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

Must Haves:

Writing and nbsp;and and nbsp;documenting and nbsp;test and nbsp;scenarios and nbsp;and and nbsp;test and nbsp;scripts
Completing and nbsp;all and nbsp;preparatory and nbsp;activities and nbsp;including and nbsp;test and nbsp;materials
Testing and nbsp;using and nbsp;imaging and nbsp;and and nbsp;data and nbsp;capture and nbsp;solutions
Documenting and nbsp;test and nbsp;results and nbsp;and and nbsp;reporting and nbsp;progress
Experience and nbsp;in and nbsp;testing and nbsp;COTS and nbsp;solution
Experience and nbsp;in and nbsp;conducting and nbsp;data and nbsp;mapping and nbsp;exercise and nbsp;and and nbsp;validation and nbsp;testing
Experience and nbsp;of and nbsp;working and nbsp;within and nbsp;OPS
Experience working with Azure DevOps

HM Note: This hybrid contract role is five (5) days in office. Candidates resumes must include first and last name.DescriptionResponsibilities: and nbsp;Good and nbsp;understanding and nbsp;of and nbsp;Quality and nbsp;Assurance and nbsp;Methodologies and nbsp;and and nbsp;Best and nbsp;Practices. a...

HM Note: This hybrid contract role is five (5) days in office. Candidates resumes must include first and last name.

Description

Responsibilities: and nbsp;

Good and nbsp;understanding and nbsp;of and nbsp;Quality and nbsp;Assurance and nbsp;Methodologies and nbsp;and and nbsp;Best and nbsp;Practices. and nbsp;
Experience and nbsp;with and nbsp;Manual and nbsp;Functional and nbsp;and and nbsp;SIT and nbsp;Testing and nbsp;using and nbsp;existing and nbsp;Test and nbsp;Cases/Scripts. and nbsp;Is and nbsp;able and nbsp;to and nbsp;create and nbsp;Test and nbsp;Cases/Scripts and nbsp;from and nbsp;predefined and nbsp;user and nbsp;Requirements. and nbsp;
Must and nbsp;be and nbsp;able and nbsp;to and nbsp;Open and nbsp;Document and nbsp;Defects and nbsp;and and nbsp;Retesting and nbsp;Defects and nbsp;using and nbsp;Defect and nbsp;Management and nbsp;Tools and nbsp;as and nbsp;well and nbsp;as and nbsp;provide and nbsp;Testing and nbsp;Status and nbsp;updates and nbsp;to and nbsp;Test and nbsp;Leads. and nbsp;
Is and nbsp;familiar and nbsp;with and nbsp;Test and nbsp;strategy and nbsp;and and nbsp;Test and nbsp;Plans. and nbsp;
Understands and nbsp;and and nbsp;Identifies and nbsp;Test and nbsp;Data and nbsp;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 Jr. System Tester/Quality Assurance Specialist is able to follow test plans test scripts and test cases and executing these against the various components
and nbsp;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 and nbsp;Skills: and nbsp;

Experience and nbsp;in and nbsp;planning and nbsp;organizing and nbsp;and and nbsp;providing and nbsp;status and nbsp;of and nbsp;testing. and nbsp;

Desirable and nbsp;Skills: and nbsp;

Knowledge and nbsp;and and nbsp;understanding and nbsp;of and nbsp;Accessibility and nbsp;for and nbsp;Ontarians and nbsp;with and nbsp;Disability and nbsp;Act and nbsp;(AODA) and nbsp;and and nbsp;related and nbsp;regulations and nbsp;and and nbsp;standards and nbsp;
Experience and nbsp;planning and nbsp;and and nbsp;organizing and nbsp;testing and nbsp;efforts and nbsp;for and nbsp;both and nbsp;large and nbsp;and and nbsp;small and nbsp;systems and nbsp;
Experience and nbsp;coding and nbsp;automated and nbsp;test and nbsp;scripts and nbsp;to and nbsp;produce and nbsp;sets and nbsp;of and nbsp;automated and nbsp;test and nbsp;cases and nbsp;
Experience and nbsp;testing and nbsp;Commercial and nbsp;Off-the and nbsp;Shelf and nbsp;Applications and nbsp;(COTS)

Skills

Experience and Skill Set Requirements

and nbsp;

Systems and nbsp;Testing/QA and nbsp;Specialized and nbsp;- and nbsp;Jr. and nbsp;details:

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

System and nbsp;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 systems compliance with its specified requirements. System testing input is all the integrated 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

and nbsp;

Integration and nbsp;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.

and nbsp;

AODA and nbsp;Testing:
The Accessibility for Ontarians with Disabilities Act (AODA) is the compliance testing required to meet the Government of Ontarios 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).

and nbsp;

Regression and nbsp;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

and nbsp;

End-to-end and nbsp;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 and nbsp;candidate and nbsp;should and nbsp;have and nbsp;demonstrated and nbsp;experience:
Writing and nbsp;and and nbsp;documenting and nbsp;test and nbsp;scenarios and nbsp;and and nbsp;test and nbsp;scripts
Completing and nbsp;all and nbsp;preparatory and nbsp;activities and nbsp;including and nbsp;test and nbsp;materials
Testing and nbsp;using and nbsp;imaging and nbsp;and and nbsp;data and nbsp;capture and nbsp;solutions
Documenting and nbsp;test and nbsp;results and nbsp;and and nbsp;reporting and nbsp;progress
Creating and nbsp;updating and nbsp;and and nbsp;monitoring and nbsp;defects and nbsp;to and nbsp;support and nbsp;defect and nbsp;triage and nbsp;and and nbsp;resolution
Updating and nbsp;business and nbsp;requirements and nbsp;documentation and nbsp;and and nbsp;participating and nbsp;in and nbsp;design and nbsp;sessions
Experience and nbsp;in and nbsp;testing and nbsp;COTS and nbsp;solution
Experience and nbsp;in and nbsp;conducting and nbsp;data and nbsp;mapping and nbsp;exercise and nbsp;and and nbsp;validation and nbsp;testing
Experience and nbsp;of and nbsp;working and nbsp;within and nbsp;OPS
Experience working with Azure DevOps

Evaluation and nbsp;Criteria:

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

Must Haves:

Writing and nbsp;and and nbsp;documenting and nbsp;test and nbsp;scenarios and nbsp;and and nbsp;test and nbsp;scripts
Completing and nbsp;all and nbsp;preparatory and nbsp;activities and nbsp;including and nbsp;test and nbsp;materials
Testing and nbsp;using and nbsp;imaging and nbsp;and and nbsp;data and nbsp;capture and nbsp;solutions
Documenting and nbsp;test and nbsp;results and nbsp;and and nbsp;reporting and nbsp;progress
Experience and nbsp;in and nbsp;testing and nbsp;COTS and nbsp;solution
Experience and nbsp;in and nbsp;conducting and nbsp;data and nbsp;mapping and nbsp;exercise and nbsp;and and nbsp;validation and nbsp;testing
Experience and nbsp;of and nbsp;working and nbsp;within and nbsp;OPS
Experience working with Azure DevOps