An Initial exploratory test for identifying and documenting existing defects in the system.
Documentation of bugs must contain as a minimum the following information: Name, Description, Steps to Reproduce, Expected Behavior & Acceptance Criteria.
In case a bug is difficult to reproduce, screenshots and/or videos can be provided as support content.
Apart from the initial exploratory test, specific tests must be made for each new feature or bug fixes the development team delivers, just as in the exploratory test, defects must be documented appropriately.
Collaboration with the development team to prevent issues in new features or ensure that a bug fix doesn't introduce unexpected behaviors.
Generate monthly reports to provide the whole team visibility related to bugs and their resolution.
Create a battery of automated Smoke tests so they can be run weekly manually or in a CI/CD pipeline automatically.
Be active in the project's management tool as a lot of what happens in tasks is handled asynchronously through the comment section.
Be ready to have meetings with the development team to discuss or clarify issues that you (QA) reported.
Be diligent with the status of tasks, if a task is moved to QA status it means is ready to be tested in the appropriate environment.
This Job is expired. The Company is no longer accepting applications for this position.
Organization Summary
We are WordPress themes and plugins development company. Besides this, we work on Laravel and custom PHP.
