Competency Name: Foundation - Testing Concepts, Process and Methodology
Broad Definition: This competency refers to the ability of the associate to understand and perform testing activities of a project
Criteria E0 E1 E2
I Criteria for defining proficiency vis-à-
vis knowledge & skills
1.Precondition Should have basic knowledge of Should have E0 proficiency in SDLC Should have E1 proficiency in SDLC
[ Expressed as a prerequisite - in terms Software Development Life Cycle.
of academic qualification AND / OR
industry experience (whichever is
applicable) AND / OR relevant
knowledge in any other competency
TCS Confidential
2. Knowledge Should have knowledge on: Should have knowledge of: Should have knowledge of:
[Expressed as Area of knowledge and
not skill, includes knowledge of process, (A)Fundamentals of: (A)Categories of Testing (A)Testing Methodologies
methodologies, concepts and tools.] 1.Testing Objectives, Quality Control, -Static & Dynamic Testing -Overview of various Testing Focus
Quality Assurance, Verification and - Other Testing Types - Alpha Testing, Areas (COTS Testing, Usability Testing,
Validation Ad hoc Testing, Beta testing, Migration Testing, Security Testing, Multi-
2.Simple Testing Types (White box, Regression Testing, Volume and Stress Platform Testing, Compatibility Testing,
Black box, Grey Box, non-functional ) Testing, Load Testing, Soak Testing, Internationalization and Localization
3.Testing Levels (Unit, Release Testing, etc. Testing, Service Testing,
System,Integration, Acceptance) Disaster/Recovery Testing etc.)
4.Testing Phases (planning, design, (B)Test Design Techniques
execution, defect reporting & closure) -Experience Based Test Design (B)Basics of Test Management
5.Testing Models (V-model, Iterative) Techniques - Test result analysis and reporting
6. Faults, Errors, Defects - Risk Based Testing, Model Based - Test environment management
Testing, Exploratory testing - Test metrics
(B)Test Design Techniques
1.Requirement Based & Structure Based (C)Basics of Test Process and (C)Test Automation Tools
Techniques documentation strategy, plan, test -Functional Testing Tools (Test
2.Boundary Value Analysis, Equivalence approach, test scenarios, test suites, Management and Test Execution)
Partitioning, Basis Path Testing test cases, test log, defect log, test result -Non-functional Testing Tools
3.Coverage Types - Statement reports, requirement traceability) (Performance, Volume, Stress, Load
Coverage, Path Coverage, Decision Testing)
g MCDC, etc.
Coverage, ((D)Basics
) of test environment
Setup,test bed setup and configuration,
(C)Basics of Test Automation test data preparation, configuration and
1.Knowhow of working on Test build processes for testing.
Execution Tools(Functional &
Performance Testing tools)
3. Experience
[Expressed as duration in months /
years wrt exposure, including breadth &
the depth of assignments; also beyond
project experience]
TCS Confidential
3.1 Type of project experience Should have prepared and executed Should have at least 12 months of work Should have more than 2 years of work
[Includes 'type' in the form of Test Cases, Test Scripts and Test Data experience in a 'Testing" project(either experience in a 'Testing" project(either
implementation, end-to-end project, as part of a training case study or POC. "Testing-only"(IV&V type) or Testing- "Testing-only"(IV&V type) or Testing-
support, roll outs, upgrades, professional also(Embedded type) projects. also(Embedded type) projects
services, consulting engagements AND /
OR the Number of projects AND / OR Should have prepared Test Cases, Test Should have performed the test
Time spent on the project ( for eg., 3 Scripts and Test Data preparation, execution and defect
consulting projects of minimum 6 tracking for (two of the following)
months duration ; 1 roll out project of at Should have executed the test and - Functional Testing
least 18 months] recorded the result(manual testing) - Product Testing
- Performance Testing
Should have logged and analysed the - Security Testing
defects - Usability Testing
- Compatibility Testing
using testing tools
3.2 Beyond project development N/A N/A Should have done EQA of testing
experience [Includes artifacts on at least 2 projects
[1) Solutioning of proposals
2) Reviews done
3) No. of contributions made to
trainings/training material]
4. Asset Creation
[Expressed as any reusable and
deployable assets created in the
knowledge management system of the
organization]
4.1 Process frameworks defined N/A N/A N/A
[Articulated as the process improvement
designed OR a new process framework
designed]
4.2 Tool creation N/A N/A N/A
[Expressed as a system or function tool
designed OR created towards improving
business delivery / learning]
TCS Confidential
4.3 Reusable & deployable assets N/A N/A Should have conributed at least 1 best
created practice or 1 reusable testing asset or
[Expressed as reusable and deployable customised test artifact template
assets created (like those in Mighty &
Knowmax]
OR
No. of training material created N/A N/A Should have created/updated minimum
[Expressed as the number of relevant one training material wrt testing
training material created towards
development of a particular body of
knowledge or skill]
5. Industry contribution
[Expressed as the contributions made to
the industry.This criteria should be
measured by mechanisms for eg: TCS
GEMS]
5.1 Recognized by Peers N/A N/A Should be recognized as a testing expert
[Expressed as the recognition given by - based on training feedback rating of
the peer community and should be 90% and higher.
measured by appropriate mechanism - or through appreciation note for helpng
such as TCS GEMS] in test design or test data design.
- or by answering satisfactorily over 5
queries per year on forums like
Knowmax and JustAsk.
AND/OR
Recognized by a Parent Body N/A N/A N/A
[Expressed as the contribution
recognized by a renowned and
recognized parent body]
AND/OR
Invited as Speakers N/A N/A N/A
[Expressed as recognition from an
external body when it extends an
invitation to the speaker to address a
recognized forum]
TCS Confidential
II Assessment / Evaluation
Methodology vis-à-vis Proficiency
Level
1. Certification Should have attended the internal Should have cleared the ISTQB Should have attended classroom Based
[Expressed as achievement of external training on Software Testing foundation/ CSTE level 1/CSQA Training on Advanced Concepts in
programs - certifying a part of the Fundamentals certification Software Testing,Functional Testing
proficiency level, Achievement of internal tool/Non-Functional Testing tool
programs - internal trainings attended]
2. Evaluation Test Should have completed the following: Should have completed the following Should have completed the following
[Expressed as a certification the
individual has to achieve towards the Self assessment Self assessment Self assessment
said proficiency level. (for eg.,Type of Learning object. Learning object Learning object
tests for each proficiency should be Supervisor Assessment
defined-like for E0 level it will be only
self assessment, for E1 it should be
panel review etc)]
Version History
Project Details: Java Solutions
Unit: Foundation Services - Assurance
Parentt Project
P P j t : : Foundation
F d ti technology
t h l Services
S i
Project Owner/GL: Vijay Shankar Krishnamoorthy (170316)
Amendment History:
Version Defined By - Role & Approved By - Role & Group Facilitated By Date
1 Janaki Ballava Vijay Shankar Krishnamoorthy (170316) Lopa Saigal 3rd Dec, 2009
Mishra Technology Excellence Group (601661)
P
Ponmalarsangeetha
TCS Confidential