QA Lead: Difference between revisions

From Avlis Wiki
Jump to navigation Jump to search
m (Spacing fix.)
m (Dev Updates!)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
You are the gate keeper.  It is your job to make sure that all the content added for the Avlis servers is bug-free before it is added. In support of this lofty goal, it is your job to organize the bug hunt when issues appear in production. You manage the building and coding guidelines, as well as the people who enforce them.  You are responsible for hiring and managing [[QA]] tester subcontractors. You make decisions and recommendations to Orleron on all Module Updater team applications.  This position reports to the Project Manager.
The Quality Assurance ([[:Category:Team:QA|QA]]) Lead ensures that all the content added for the Avlis servers is bug-free before it is added. In support of this lofty goal, it is their job to organize the bug hunt when issues appear in production. As such, the QA Lead maintains QA policies and processes, and is responsible for hiring and managing [[QA]] tester subcontractors. The QA Lead is also responsible for preparing & documenting module & other content updates. Updates are ultimately published to [https://avlis.org/viewtopic.php?f=78&t=8245&start=1100 Development Updates] on avlis.org.
 
* The Avlis QA Lead position is currently maintained by: [[User:MadK@|MadK@]]
 
 


<!--
===<b><u>Responsibilities</u></b>===
===<b><u>Responsibilities</u></b>===
*Hire, promote and task QA subcontractors and Module Updaters.
*Hire, promote and task QA subcontractors and Module Updaters.
Line 22: Line 19:


===<b><u>Job Description</u></b>===
===<b><u>Job Description</u></b>===
It is your responsibility to ensure we have active Module Updaters.  When these positions needs to be filled due to a vacancy or inactivity, it will be your responsibility to advertise for the position(s), gather applications and send them to the Project Manager for discussion and review.  Final decision will be made by you and the Project Manager and approved by Orleron. It is then your responsibility to ensure an acceptance or rejection email is sent to all applicants as appropriate. Applicants should expect to get a final response within two weeks of submitting their application.
It is your responsibility to ensure we have active [[Module Updater|Module Updaters]].  When these positions needs to be filled due to a vacancy or inactivity, it will be your responsibility to advertise for the position(s), gather applications and send them to the [[:Category:Team:Admin_Staff|Admin Staff]] for discussion and review. It is then your responsibility to ensure an acceptance or rejection email is sent to all applicants as appropriate. Applicants should expect to get a final response within two weeks of submitting their application.


You are also responsible for hiring subcontractors to act as Quality Assurance testers as needed and/or requisitioning existing available subcontractor resources from the Project Manager.  It is your responsibility to train new testers and assign projects to be tested in the order assigned by the Project Manager.  It is further the responsibility of you and your QA team to reproduce bugs as necessary when directed to do so by the Project Manager, or when you see a need and have time.
You are also responsible for hiring subcontractors to act as Quality Assurance testers as needed and/or requisitioning existing available subcontractor resources from the Project Manager.  It is your responsibility to train new testers and assign projects to be tested in the order assigned by the Project Manager.  It is further the responsibility of you and your QA team to reproduce bugs as necessary when directed to do so by the Project Manager, or when you see a need and have time.


The QA Lead is responsible for managing the bug tracking databse, including keeping up with bugs and assigning and revoking bug DB privelages to Team Members.  You will work with the Project Manager to make sure that the Team keeps on top of important and highly visible bugs.
The QA Lead is responsible for managing the bug tracking database, including keeping up with bugs and assigning and revoking bug DB privelages to Team Members.  You will work with the Project Manager to make sure that the Team keeps on top of important and highly visible bugs.


You are responsible for maintaining the building and coding guidelines.  The QA group will be responsible, under your direction, with ensuring the building, coding and erf import guidelines are followed.  You are the final authority on what goes into a module.  Nothing goes to production without your approval.
You are responsible for maintaining the building and coding guidelines.  The QA group will be responsible, under your direction, with ensuring the building, coding and erf import guidelines are followed.  You are the final authority on what goes into a module.  Nothing goes to production without your approval.
Line 35: Line 32:


===<b><u>Application</u></b>===
===<b><u>Application</u></b>===
* Contact the  [http://www.avlis.org/ucp.php?i=pm&mode=compose&g=26549 Admin Staff group] on the Avlis forum to request a current application. This is an example.
Avlis Boards Name:
Avlis Boards Name:


Line 74: Line 74:


Do you have anything else to add?
Do you have anything else to add?
-->
[[Category:Team:QA]]
[[Category:Team:Admin_Staff]]

Latest revision as of 19:19, 23 November 2021

The Quality Assurance (QA) Lead ensures that all the content added for the Avlis servers is bug-free before it is added. In support of this lofty goal, it is their job to organize the bug hunt when issues appear in production. As such, the QA Lead maintains QA policies and processes, and is responsible for hiring and managing QA tester subcontractors. The QA Lead is also responsible for preparing & documenting module & other content updates. Updates are ultimately published to Development Updates on avlis.org.