Web testingFunctionality testing of software is testing conducted on a complete, integrated system to

evaluate the systems compliance with its specified requirements.

Data base testing is very important because if the backend malfunctions, it may cause system dead lock, data
corruption, data loss and bad performance. Data integrity testing verifies that the converted data is accurate and
function correctly within a given application. Testing data integrity is the only way to ascertain that the stored
data is complete, correct and consistent. Data base output testingz( form view, list/ table view and report view)
In functional testing( business work flow) test the end to end work flow / business scenerios which takes the user
through the series of webpages to complete.
Usability testing evaluate the degree to which the user can interact effectively with the web
application. Usuability test are designed by web engineering team , but the test themselves are conducted by end
users.( designing activitities comes under this testing) look and feel consistency and content verification will comes
under this testing.
In accessibility testing ( identify the check points for accessibility) priority1( satisfy the checkpoints is basic
requirement to use web documents)p2(satisfy checkpoints will remove significant barriers in access web
documents)p3( satisfy check point will improve access to web document). Perform html and css validation using
validators these tests will ensure that the undellying code is error free. Task based testing will comes under
accessibility testing.
Graphical user interface is the front end that serves as an interface for the end users when in any kind
of information process and data storage.( multiple windows, visual interface,flexibility to move into many
application areas, seamless integration between the packaged and customized application.( all types of boxes and
dropdown will come under this.
Interface testing which ensures the interface between the concerned clients and servers execute in
tandem.(appliacation + business analysis = interface analysis). Server interface( communication is done correctly
between web server and application server, application server and database server and vice versa.)External
interface( ensure all the supported browsers have been tested).internal interface( ensures all linked documents
are opened/ supported in all platforms.network failures, intelligent error handling, network failures). Printer
interface
Content managemet testing is performed to ensure that all the pages of the website display correctly,links go to
the specified address and images are not broken.
Web security testing( is the process that determines that the confidential data stays confidential and user can
perform those tasks they are authorized to perform.phishing is typically carried out by email spoofying or
instant messaging and it often direct users to enter details at the fake website whose look and feel are almost
identical.Standard compliance testing(html validation,css validation,
OATS:Oats can be used to reduce the number of test combinations and provide maximum test coverage with
minimum number of test cases. Oats is the systematical and statistical way of testing pair wise interactions by
deriving small set of test cases from large number of scenarios. Terminology( runs( no of rows), factors(columns
or variables), levels( max no of values that can be taken on by single factor)
L(runs)(levels)(factors)
Oats is simpler to generate and less error prone than test sets created manually. Merits(early defect detection,
regression, productivity improvement, quality effort saving)
Donts in oats( manually, high risk applications, dependency of variables or columns)
ALL PAIRS TOOL:All pair is a command line executable tool based on perl script. It is similar to oats.it uses all pair
technique.it doesnt go beyond two factor interface. Doesnt allow dependency.
TNO( the next generation oats) generates all possible combinations, upto nth level of interaction,
DEFECT:Application defects(coding errors, incomplete requirements, incomplete or enormous documentation,
incorrect interpretation of requiremendts, missed requirements)
Defect summary report( lists of defects, categorize the defects, risks, for cast planning)
Defect leakage =( no of defects attributed to the stage but only captured in subsequent stages)/( total no of
defects captured in that stage + total no of defects attributed to a stage and captured in subsequent stages)
Defect analysis is also called as casual analysis which is used to find root cause.
Pareto analysis is statistical technique in decision making that is used for the selection of limited number of task
that produces significant overall effect. Based on 80/20 rule. It helps to find frequency of occurance of defect type
or problem.
Cause effect includes brain stroming.
Test design: Test requirement is nothing but the software or business req document/ use case document
containing the functional specifications or business applications from which test conditions or test scenarios are
derived,
Risk based testing: Rbt frame work( test optimal, test critical, early defect catch, save cost, design less).this
involves four phases ( prioritization, test coverage analysis, implementation, risk reassessment and reporting)
Probability of failure =( probability of risk factor weightage * risk factor value)/ rfw
Test coverage optimization ( extent of testing, inefficiency of excessive testing, maintainence of high level
application quality)
Risk reassessmet and reporting( defect analysis, coverage validation, reporting)
Use case purpose:Detailed understanding of requirements, helps to identify capsules to encapsulate the data,
promoting communication, focusing on what rather than how, providing prototype test cases.
Text description is the meat of the use case.
Precondition specifies the required state of the system prior to the start of the use case. This can be used similar
purpose in the test case.
Post condition is the state of the system after user interaction.this may be used for test pass or fail critetria.
The event flow is a description of the steps of the actors interaction with the system and systems required
response.
To ensure maximum coverage follow the control flow diagram or flow chart.
Try to cover negative/error scenarios first and then positive scenarios. Positive scenario have to be tested first.
Test cases should test how your system should work not what it actually does.
In severe time pressure exploratory testing is performed.
Decision coverage is also known as branch coverage, all edge coverage, basic path coverage, c2 coverage,
decision-decisiion path testing.
Equilance class is the subset of data which is representive of larger classes.
Optimization techniques used in cognizant OATS( systematic way of testing pair wise interaction when there are
multiple values to be tested)(coverage increases, productivity,quicker to market). MCDC( modified condition or
decision coverage)( used in high level of decision coverage classes).Metrics allow for deeper understanding of
performance of the testing team including their effectiveness and efficiency
Test design productivity(test case creation productivity of the team.)it is the measure of teams efficiency in
designing test cases.
Tdp= no of test cases prepared/(preparation effort + review effort + review effort for design)
Casual analysis resolution(CAR) can be initiated to identify the low productivity.
Test design coverage( indicates completeness of test suite by tracking them back to every testable requirement to
ensure that all the requirements are converted into tc and test conditions and there is no gap in the coverage.
TDC= total no of testable requirement mapped to the test cases/(total no of baseline requirements) * 100
Exclusive peer review and sme review can be brought into test design phase to test the coverage of the design as
against the requirements.

Review defect density ( this metric indicates the test case creation productivity of the team. The base measure of
the metric is the count of test cases/ test script designed in time and time/effort spent on test design.
It is the measure of the teams efficiency in designing test cases without review defects.
Rdd= total no of review defects/ actual project size
CAR analysis can be initiated to find the root cause. Review checklist can be prepared and circulated to improve
the quality of test cases.
Review efficiency :This metric indicates how effectively the review process has performed in the project. The
base measure of the metric is the count of review defects overall/ stage wise , count of review defects leaked to
the subsequent stages.
RE= ( total no of pre shipment review defects /( total no of pre shipment review defects+ total no of post shipment
review defects)*100
Exclusive peer review and sme review is used to eliminate all the review defects in subsequent stages.
Batch testing:Batch processing is done when the data is in large volume or the task is complex one. Eg. Payroll
system in the company
Main frame testing is the client server application testing. Two types( batch testing(back end process) and online
testing( front end process done through various online transaction processing(oltp))
Batch testing is usually jcl( job controllanguage(Z/OS OR OS/390) and written to handle jobs with in code itself
ie jobs that can run without user interaction are called batch jobs. A program that reads large file and generate a
report is considered to be the batch job.
Jcl is the means of communication between application program and os. Jcl is not used to write computer
programs.
JES2 AND 3 are the batch processing environments
Positional parameter = ( accouting information(identify the area that the computer time is to be charged for this
job) + programmer name( used for the identification of routing printouts)
Web based testing: Consistency testing checks standardized look and feel of across the application( usability
testing).
Accessibilty testing means testing against the guidelines of the web page and web application.
Gui is the front end that serves as an front end that serves as an interface for the end users when any kind of the
information processing and storage.
Gui testing can refer to just ensuring the look and feel of the application is acceptable to end user or it can be
refer to testing the functionality of the each and every component involved.
Data integrity testing verifies that converted data is accurate and functions correctly within a given application. It
is the only way to ascertain that stored data is accurate,complete and consistent.
Data validation check is for checking errors such as wrong type of data, data values are too big or too small.
Verification check is data accuracy.
Compatibility testing is the critical testing in the web application testing. Two types( cross browser and cross
platform (OS))
A performance test is the technical investigation done to determine or validate the responsiveness , speed
scalability or stability characteristics of the product under test.
Load testing are end to end performance tests under anticipated production load. This is QA type test.this is
business technology optimization type test.
Stress testing is performed to identify the application defects that surfaces only under high load conditions like
synchronization issues , race conditions and memory leaks.
Capacity testing is conducted in conjunction with capacity planning ,which is used to plan for future growth such as
increased user base or increased volume of data.it provides information about how work load can be handled to
meet business requirements.
Performance testing tools: Silk performer :- it is enterprise class tool for software application performance and
load testing. Load, stress and performance in open and sharable mode. We can create powerful and realistic load
tests for thousand of the users running business scenarios across broad range of enterprise application
environment to identify bottle necks and then apply powerful diagnosis to resolve performance issues.
Rational performance tester :- presence and cause of system performance bottle necks. It goes beyond
problem identification to problem diagonis uses root cause analysis.
Qtest :- integrates into entire application development and quality control cycle. Operating annamolies are
identified and analyzed to identify the immediate correction. Testing in wide range of projects in different
environments.
HP load runner :- detect bootle neck before new system or upgraded. It lets us to deploy quality application with
confidence and enables consistent repeatable testing process.
Device testing :- includes interface testing, functional testing, usability testing, performance and stress testing.( os
perspective, end-user, hardware and others perspective).
Quality engineering: Qe is providing complete engineering solution to the problem, in additional to functional
code , a complete engineering solution includes a suite of automated tests, documentation, sample code
and support.
Continuous integration :- is one of the badeline frame work approach in the recent development of
quality engineering and automation. It aims at improve the quality of the software and to reduce the time taken
to deliver it, by replacing the traditional practice of applying quality control after completing all development. It
implement continuous process of applying quality control- small pieces of effort, applied frequently.
Qc: Test plan stores all the test cases for testing the functionality under test.
Test subject( divide application into functionality to be tested)
Test lab module where we can schedule and execute test cases based on test execution plan. We can create
test set trees.
Defect tracking :- key tasks( add defects, review new defects,repair open defect, retest defects, analyze defect
data). We can associate an existing defect using the id or by select option.
Reports on defects with linked tests and runs will be in fixed or rejected status.
Defect progress graph shows the accumulation of the defects in the qc projects or the estimated or actual
amount of time taken to fix these defets, at specific point during a period of time.
Qc will enable user to create and manage entities ,securing the previous version of those entities.( business
requirement, business models, test plan and test resources are get versioned)
Baseline:- it is the snapshort of the library( project entities) at a specific point of time; primirarly used to track and
compare the changes made at all stages of the application development.( req, test, test resources and business
components will get baselined) same for assest sharing.
Releases are major project builds and cycle corresponding to micro iteration within a build.
Risk based quality management:-
Risk analysis process(assess requirements, define testing policy settings, finalize testing policy, analyze testing
strategy)
Risk based testing(enables us to calculate at which level to test each requirement, based on the nature of the
requirement and the resources u have available.
Defect flow( new, open( deffer,reject,duplicate),assigned, fixed, retest,close or reopen(assigned).
Qc addins( explorer, synchronizer,word, excel)
Qc dev collaboration (ellipse(traceability between requirements, defects and source code), visual
studio(bidirectional synchronization of qc req and defects) collabnet( bidirectional synchronization of qc user
stories to team forge work task)
Cognizant 2.0it is an end to end integrated global delivery ecosystem which connects cognizant, its client and
vendor on a single platform to optimize delivery through a blend of collobration, work flow automation process
orchestration and knowledge management.
Mash up UI home is the one stop place to view activities across application.
Public stream will have the blogs, ctweeted posted by all the resources from cognizant.
My stream will have blogs , ctweets posted by you.
Community stream will have blogs, ctweets q nd a, documents posted in the community in which you belong to.
Network stream will have the blogs, ctweets, qnd a, documents posted by resources whom you follow or
resources who follow you.
Process space has details of the process package includes number of phases which are divided into activities and
tasks,
Process package(details of work product,guidelines, check lists) we can aslo view trailoring guidelines, testing and
review tasks, glossary of term used, change history of package) bench mark values can be reffered from this page.
A new project created in ESA will automatically get updated in c20
Project setup will have all the basic details of a project like the project id start and end dates etc resource
management and sub project are also be there,. Onsite and offshore details. IE factor and audit status, sub
projects also be there
C2 guides the project planning activity by inheriting the process to create WBS( work breakdown structure).wbs
is created in the form of WMP( work management plan). Wbs can be created for phase, process or all phases.
Metric plan can be created once process package is approved.the goal values for the metric plan are standard
OLBM/PLBM based on process package. Metric plan is reviewed by quality reviewer/ quality champion then
approved by pm. Metric analysis can be viewed after 6 hours after metric actual approved.
Define project scope page enables to configure defect management (defects as work type or dwt) or configurable
issue management( issue as work type or iwt) for a new project marked as tracking project.
Discussion forum can be integrated with outlook, it is possible to post and reply to the message from outlook.
SQL: Collection of interrelated data is called dbms( relational, network, hierarchical, object, object relational)
Functions of dbms ( data definition, data manipulation, data security and integrity, data recovery and
concurrency, data dictionary and performance)
Defect :Managing defect( identification, investigation, analyze, loging , tracking, predicting)
Defect prevention has direct impact on controlling the cost of the project and quality of deliverables.
Casual analysis is done in review defects, application defects leaked to uat, rejected application defects.
In c20-create defects.
QC: Tools in qc ( changing password, changing user settings)Key task for planning tests( design test
steps, automate tests, analyze tests). Defect module( new defect) test lab( add defect). Useful apps in qc are used
for data manipulation and data retrival.Version control( req, business model, test plan, test resources). PMD-
programming mistake detector- checks standard programming principles.
Find bugs is static analysis tool that examines your class or jar files looking for potential problems by matching
your byte code against a list of bug patterns.Check style- development tool to help programmer to write java
code that adheres to a coding standards. Main functionality is to check code layout issues, to find class design
problems,duplicate code or bug pattern like double checked locking.
Junit and mock objects(java) nunit and n mock in ( .net). Pre requisite for enabling metric module(testing, process
package should be full ownership v2.1 or testing full ownershio v3.0, project should be tracking level project(no
sub folders). Once the pp has been approved , testing metrics enablement can be done only after 24 hours.
Metric setup wizard has all list of metrics and their formulae. Metric frequency( updation( current and previous
three periods), standard( auto c20), custom( for future release, calculated( need user inputs)
Phc linked(metric submitted in testing metric module only be considered for phs rating. Non-beta project will still
continue to submit metrics in prolite. Inclusion of bic metrics(6 new bic has been included,rework effort, rework
efficiency, cost of quality, prevention coq, failure coq, appraisal coq.). Adapart is the test design machine of
cognizant.(create project, create req,diagram creation, attach test step, compile and publish to database, priotrize
scenarios, test suite creation, optimize test suites