0% found this document useful (0 votes)
10 views

Digital _ DevOps Testing

The document outlines the competency framework for Digital DevOps Testing, detailing proficiency criteria across three levels: E0, E1, and E2. It specifies prerequisites, knowledge requirements, project experience, asset creation, and industry contributions necessary for each level. Additionally, it includes assessment methodologies for evaluating proficiency, such as certifications and evaluation tests.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views

Digital _ DevOps Testing

The document outlines the competency framework for Digital DevOps Testing, detailing proficiency criteria across three levels: E0, E1, and E2. It specifies prerequisites, knowledge requirements, project experience, asset creation, and industry contributions necessary for each level. Additionally, it includes assessment methodologies for evaluating proficiency, such as certifications and evaluation tests.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Competency Name: Digital : DevOps Testing

Broad Definition: This competency refers to the ability of an associate to work with tools such as Nightwatch, Cucumber, Artillery, and so on that are
used in DevOps Projects.
Criteria E0 E1 E2
I Criteria for defining proficiency vis-à-vis
knowledge & skills
1.Precondition Should have good understanding of Should satisy conditions of all previous Should satisy conditions of all previous level
[ Expressed as a prerequisite - in terms of Devops culture, lifecycle, and processes. level
academic qualification AND / OR industry
experience (whichever is applicable) AND / OR
relevant knowledge in any other competency

2. Knowledge Exposure to DevOps projects and usage Working knowledge in implementing / Good knowledge in deciding the right testing
[Expressed as Area of knowledge and not skill, of testing tools such as Nightwatch, configuration the tools for automating tool that suits the project requirement.
includes knowledge of process, methodologies, Cucumber and Artillery for end to end the testing as part of the DevOps Configuring and implementing the tool as part
concepts and tools.] testing of browser based apps or for deployment pipeline. of the DevOps deployment pipeline to automate
automated user acceptance or for load the testing.
testing of applications.

3. Experience NA NA NA
[Expressed as duration in months / years wrt
exposure, including breadth & the depth of
assignments; also beyond project experience]

3.1 Type of project experience Should have experience of 0-6 months Should have experience of 6-18 Should have a minimum 2 years experience
[Includes 'type' in the form of implementation, end- working in DevOps projects months working in DevOps projects working in DevOps projects
to-end project, support, roll outs, upgrades,
professional services, consulting engagements
AND / OR the Number of projects AND / OR
Time spent on the project ( for e.g.., 3 consulting
projects of minimum 6 months duration ; 1 roll out
project of at least 18 months]

3.2 Beyond project development experience NA NA Should have conducted training on various
[Includes DevOps testing tools
[1) Solutioning of proposals
2) Reviews done
3) No. of contributions made to trainings/training
material]

4. Asset Creation NA NA NA
[Expressed as any reusable and deployable
assets created in the knowledge management
system of the organization]

TCS Confidential
4.1 Process frameworks defined NA NA Should have enhanced at least 1 architecture/
[Articulated as the process improvement estimations / process templates/ framework
designed OR a new process framework related to testing in DevOps Pipeline.
designed]

4.2 Tool creation NA NA Should have contributed in creation of at least


[Expressed as a system or function tool designed one value add.
OR created towards improving business delivery /
learning]

4.3 Reusable & deployable assets created NA NA Should have prepared minimum 1 case profiles
[Expressed as reusable and deployable assets / lessons learnt / help documents /reusable
created (like those in Mighty & Knowmax] components relevant to testing solutions in
DevOps projects.
OR
No. of training material created NA NA NA
[Expressed as the number of relevant training
material created towards development of a
particular body of knowledge or skill]
5. Industry contribution NA NA NA
[Expressed as the contributions made to the
industry. This criteria should be measured by
mechanisms for e.g.: TCS GEMS]
5.1 Recognized by Peers NA NA Should have contributed to cross-collaboration
[Expressed as the recognition given by the peer and supported projects with appropriate
community and should be measured by guidance to implement testing solutions.
appropriate mechanism such as TCS GEMS]
AND/OR
Recognized by a Parent Body NA NA Externally recognized document or similar
[Expressed as the contribution recognized by a
renowned and recognized parent body]
AND/OR
Invited as Speakers NA NA Should have contributed to various developer
[Expressed as recognition from an external body communities and recognized as SME by the
when it extends an invitation to the speaker to units.
address a recognized forum]

II Assessment / Evaluation Methodology vis-à-


vis Proficiency Level

TCS Confidential
1. Certification NA As defined in LO. As defined in LO.
[Expressed as achievement of external programs
- certifying a part of the proficiency level,
Achievement of internal programs - internal
trainings attended]

2. Evaluation Test NA As defined in LO. As defined in LO.


[Expressed as a certification the individual has to
achieve towards the said proficiency level. (for
eg.,Type of tests for each proficiency should be
defined-like for E0 level it will be only self
assessment, for E1 it should be panel review
etc)]
Version History
Project Details: Fresco Play
Unit: Fresco
Parent Project : Fresco PLAY
Project Owner/GL: S Janardhan : 121494
Amendment History:
Version Defined By - Role & Group Approved By - Role & Group Facilitated by
Anupama M (119131) S Janardhan(121494) Shreedas Joseph (697259)
1 iEvolveTalent Development
22nd Mar, 2019

TCS Confidential

You might also like