QA Automation: Difference between revisions

From Secure Group Wiki
Jump to navigation Jump to search
No edit summary
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
Our QA Automation employees are responsible for developing and executing exploratory and automated tests. QA Automation Developers' responsibilities also include designing and implementing tests, debugging and defining corrective actions to ensure the highest product quality. They also review system requirements and track quality assurance metrics (e.g. defect densities and open defect counts.)
The QA Automation engineers are responsible for producing a powerful set of test cases and internal testing tools to support the development of our operating system. They help us increase the efficiency of our quality testing by developing scripts that automate test cases for key product features.


This is a very important role in our company's product development process so they have an interface with a variety of teams. Our QAs conduct tests before the product's launch to ensure the software is running smoothly and meets our partner's needs while focusing on being cost-effective. Ultimately, they monitor all stages of software development to identify and resolve system malfunctions to meet quality standards and to automate the biggest amount of features and processes.
Our QAs design and implement such tests, debug and define corrective actions to ensure the highest product quality. They are also key players to ensure collaboration with other members of the engineering team to find the best methods for solving problems and securing the quality and usability of our products.


In order to progress in our development path and Level Up or Step Up, our QA Automation Developers must:</br>
Developing in this framework means closely monitoring the software development process to identify what are its automation possibilities to ultimately ensure our testing capacity works at its full potential and to ensure the quality of our solutions.
* Meet the criteria of the Level & Step Chart for the [[Individual_Contributors|Individual Contributors Path]]
 
* Score at least 4 in the [[KAI]] of their position in order to reach Level 3
= Progression=
In order to progress in our development path and Level Up or Step Up, our QA Automation team must:
* Meet the criteria of the Level & Step Chart for the [[Performance#Individual_Contributors_Levels|Individual Contributors Path]]
* Meet the [[QA_Automation#KAI_of_the_framework|KAI]] grade of the framework related to each level
* Demonstrate proficiency in [[Secure Group Knowledge]]
* Demonstrate proficiency in [[Secure Group Knowledge]]
</br>
</br>


<div class="center">
= Salary Grid =
= Salary Grid =
All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.
All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.
Line 25: Line 27:
!4
!4
|-
|-
!QA Automation Developer
!1
|4.000
|4.500
|4.150
|4.650
|4.300
|4.800
|4.450
|4.950
|-
|-
!Sr. QA Automation Developer lvl II
!2
|5.000
|5.500
|5.150
|5.650
|5.300
|5.800
|5.450
|5.950
|-
|-
!Sr. QA Automation Developer lvl III
!3
|6.000
|6.500
|6.150
|6.650
|6.300
|6.800
|6.450
|6.950
|-
|-
!Sr. QA Automation Developer lvl IV
!4
|7.000
|7.500
|7.150
|7.650
|7.300
|7.800
|7.450
|7.950
|-
|-
!Sr. QA Automation Developer lvl V
!5
|8.000
|8.500
|8.150
|8.650
|8.300
|8.800
|8.450
|8.950
|-
|-
!Sr. QA Automation Developer lvl VI
!6
|9.000
|9.500
|9.150
|9.650
|9.300
|9.800
|9.450
|9.950
|}
|}
</div>
</div>
</div>
</div>


= [[Knowledge_Management#Knowledge_Accountability_Index|KAI]] of the position =
= [[Knowledge_Management#Knowledge_Accountability_Index|KAI]] of the framework =
 
<!-- JOB FRAMEWORK -->
<div class="grid two-columns">
<div class="">
  <div class="box-header center">
== Extensive Knowledge ==
== Extensive Knowledge ==
   </div>
   </div>
   <div class="box-content framework">
   <div class="box-content framework">
     <div class="center">
     <div class="center">
{| class="wikitable" style="text-align:center; background-color:#DEEBFF; color:#222;"
{| class="wikitable" style="text-align:center; font-size:11px; font-family:Arial, Helvetica, sans-serif !important;; background-color:#DEEBFF; color:#222;"
|- style="font-weight:bold; background-color:#F4F5F7; color:#172B4D;"
|- style="font-weight:bold; vertical-align:middle; background-color:#EAECF0; color:#172B4D;"
! rowspan="2" | Type
! rowspan="2" | Type
! rowspan="2" | Knowledge Description
! rowspan="2" | Knowledge Description
! colspan="6" | Minimum Grade to acquire Level X
! colspan="6" | Minimum Grade to acquire Level X
|- style="font-weight:bold; background-color:#F4F5F7; color:#172B4D;"
|- style="font-weight:bold; vertical-align:middle; background-color:#F4F5F7; color:#172B4D;"
| Level 1
| Level 1
| Level 2
| Level 2
Line 87: Line 84:
| Level 6
| Level 6
|-
|-
| rowspan="6" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:left;" | Frameworks
| rowspan="6" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:center;" | Frameworks
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [http://casperjs.org/ CasperJS]
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [http://casperjs.org/ CasperJS]
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
Line 136: Line 133:
| Applied theory
| Applied theory
|-
|-
| rowspan="6" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:left;" | Protocols
| rowspan="7" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:center;" | Protocols
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/SIP_(software) SIP]
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/SIP_(software) SIP]
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
Line 193: Line 190:
| Applied theory
| Applied theory
|-
|-
| rowspan="9" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:left;" | Programming languages
| rowspan="9" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:center;" | Programming languages
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Bash_(Unix_shell) Bash Script]
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Bash_(Unix_shell) Bash Script]
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
Line 266: Line 263:
| Applied theory
| Applied theory
|-
|-
| rowspan="6" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:left;" | Libraries
| rowspan="6" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:center;" | Libraries
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Linphone Linphone]
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Linphone Linphone]
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
Line 283: Line 280:
| Applied theory
| Applied theory
|-
|-
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Mockito Mockito], [https://developer.android.com/training/testing/espresso Espresso]
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Mockito Mockito] or [https://developer.android.com/training/testing/espresso Espresso]
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
Line 315: Line 312:
| Applied theory
| Applied theory
|-
|-
| rowspan="16" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:left;" | Software/Tools/Platforms <br />
| rowspan="16" style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:center;" | Software/Tools/Platforms <br />
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Apache_Tomcat Apache Tomcat]
| style="background-color:#FFF; color:#0052CC; text-align:left;" | [https://en.wikipedia.org/wiki/Apache_Tomcat Apache Tomcat]
| style="background-color:#E3FCEF;" | Practical application
| style="background-color:#E3FCEF;" | Practical application
Line 444: Line 441:
| Applied theory
| Applied theory
|-
|-
| style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:left;" | Languages (idioms)
| style="font-weight:bold; background-color:#F4F5F7; color:#172B4D; text-align:center;" | Languages (idioms)
| style="background-color:#FFF; color:#172B4D; text-align:left;" | Advanced Business English
| style="background-color:#FFF; color:#172B4D; text-align:left;" | Advanced Business English
| style="background-color:#FFFAE5;" | Limited experience
| style="background-color:#FFFAE5;" | Limited experience

Latest revision as of 08:09, 6 October 2022

The QA Automation engineers are responsible for producing a powerful set of test cases and internal testing tools to support the development of our operating system. They help us increase the efficiency of our quality testing by developing scripts that automate test cases for key product features.

Our QAs design and implement such tests, debug and define corrective actions to ensure the highest product quality. They are also key players to ensure collaboration with other members of the engineering team to find the best methods for solving problems and securing the quality and usability of our products.

Developing in this framework means closely monitoring the software development process to identify what are its automation possibilities to ultimately ensure our testing capacity works at its full potential and to ensure the quality of our solutions.

Progression

In order to progress in our development path and Level Up or Step Up, our QA Automation team must:


Salary Grid

All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.

QA Automation Step
Level
Individual Contributor Path 1 2 3 4
1 4.500 4.650 4.800 4.950
2 5.500 5.650 5.800 5.950
3 6.500 6.650 6.800 6.950
4 7.500 7.650 7.800 7.950
5 8.500 8.650 8.800 8.950
6 9.500 9.650 9.800 9.950

KAI of the framework

Extensive Knowledge

Type Knowledge Description Minimum Grade to acquire Level X
Level 1 Level 2 Level 3 Level 4 Level 5 Level 6
Frameworks CasperJS Practical application Practical application Applied theory Applied theory Applied theory Applied theory
JUnit Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Espresso Practical application Practical application Applied theory Applied theory Applied theory Applied theory
PHPUnit Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Scrum Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
TestNG Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Protocols SIP Practical application Practical application Applied theory Applied theory Applied theory Applied theory
XMPP Practical application Practical application Applied theory Applied theory Applied theory Applied theory
ZRTP Practical application Practical application Applied theory Applied theory Applied theory Applied theory
PGP Practical application Practical application Applied theory Applied theory Applied theory Applied theory
OTR Practical application Practical application Applied theory Applied theory Applied theory Applied theory
OMEMO Practical application Practical application Applied theory Applied theory Applied theory Applied theory
SSL Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Programming languages Bash Script Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Command line Practical application Practical application Applied theory Applied theory Applied theory Applied theory
CSS Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
HTML Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
Java Practical application Practical application Applied theory Applied theory Applied theory Applied theory
JavaScript Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Kotlin Practical application Practical application Applied theory Applied theory Applied theory Applied theory
PHP Practical application Practical application Applied theory Applied theory Applied theory Applied theory
XML Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Libraries Linphone Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Microsoft Exchange Web Services Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Mockito or Espresso Practical application Practical application Applied theory Applied theory Applied theory Applied theory
SMACK Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Wood Solutions Timber Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Zetetic SQL Cipher Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Software/Tools/Platforms
Apache Tomcat Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Appium Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Atlassian Bamboo Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Countly Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Docker Engine/Container Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
Elasticsearch Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
Git Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Instabug Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Kamailio Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Microsoft Azure Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Openfire Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Samsung Knox Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
Selenium Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Secure Manager Practical application Practical application Applied theory Applied theory Applied theory Applied theory
SAS Practical application Practical application Applied theory Applied theory Applied theory Applied theory
SQuirrel SQL client Practical application Practical application Applied theory Applied theory Applied theory Applied theory
Languages (idioms) Advanced Business English Limited experience Limited experience Practical application Applied theory Applied theory Applied theory
Retrieved from "https://managementmodel.info/index.php?title=QA_Automation&oldid=3475"