QA and Testing Department: Difference between revisions
No edit summary Tag: Manual revert |
mNo edit summary |
||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=About QA and Testing Department= | =About QA and Testing Department= | ||
[[Schedule of QA and Testing Department]] | |||
QA and Testing Department is a unit of IT Department, which deals with the software testing process. | QA and Testing Department is a unit of IT Department, which deals with the software testing process. | ||
| Line 17: | Line 19: | ||
|} | |} | ||
= | =Responsibilities of QA and Testing department= | ||
[[Responsibilities QA department]] | |||
* [[Responsibilities QA department#Responsibilities Head of QA and Testing Department|Responsibilities Head of QA and Testing Department]] | |||
* [[Responsibilities QA department#Responsibilities of QA Analyst|Responsibilities of QA Analyst]] | |||
=Plans= | =Plans= | ||
| Line 25: | Line 30: | ||
Here you can read our [[plans for automation]] | Here you can read our [[plans for automation]] | ||
= | =Instructions= | ||
Here you can read recommendations on how to create [[Effective Bug Report]] | Here you can read recommendations on how to create [[Effective Bug Report]] | ||
| Line 31: | Line 36: | ||
Here you can read recommendations about [[Testing process for tickets (tasks)]] | Here you can read recommendations about [[Testing process for tickets (tasks)]] | ||
Here you can read recommendations about [[Testing Techniques]] using on the Projects | |||
[[Instructions on how to create a new driver]] | [[Instructions on how to create a new driver]] | ||
[[Instructions for substitution]] | |||
=Checklists= | =Checklists= | ||
Checklist-based testing: an experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified. | [[Checklist Testing|Checklist-based testing]]: an experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified. | ||
[[Checklist Web (critical)]] | [[Checklist Web (critical)]] | ||
| Line 56: | Line 65: | ||
[[Other Admin modules]] | [[Other Admin modules]] | ||
[[Cheklist for driver app]] | [[Cheklist for driver app|Checklist for driver app]] | ||
=Test-cases= | =Test-cases= | ||
A | A [[Test Case Testing|Test Case]] is a singular set of actions or instructions for a tester to perform that validates a specific aspect of a product or application functionality. | ||
Latest revision as of 09:03, 5 June 2025
About QA and Testing Department
Schedule of QA and Testing Department
QA and Testing Department is a unit of IT Department, which deals with the software testing process.
The main goal of the Department is to ensure the high quality of the product and its compliance with the requirements.
| Software QA Analyst | Skype link | Location | |
|---|---|---|---|
| Svitlana Horbatiuk | svitlana.horbatiuk@bloomex.ca | live:.cid.a2b3a74a6e127b98 | Canada, Vancouver |
Responsibilities of QA and Testing department
Responsibilities QA department
Plans
Here you can read our plans for automation
Instructions
Here you can read recommendations on how to create Effective Bug Report
Here you can read recommendations on how to conduct Preliminary analytics during website testing
Here you can read recommendations about Testing process for tickets (tasks)
Here you can read recommendations about Testing Techniques using on the Projects
Instructions on how to create a new driver
Checklists
Checklist-based testing: an experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.
Checklist Adm-eu.necs.ca (Full)
Checklist Adm-eu.necs.ca (Critical)
Test-cases
A Test Case is a singular set of actions or instructions for a tester to perform that validates a specific aspect of a product or application functionality.
Testing delivery scenario (Canada)
Testing delivery scenario (Australia)
Release notes
Release notes contain information about new tasks and fixes, which were realized.