Saturday

Basic Computer:
Computer System: A Computer System consists of Hardware and
Software.
Hardware: Computer Hardware is any physical device, something that is
able to touch.
Software: Software is a collection of instructions and code installed into the
computer and cannot be touched.
Computer Software: Computer Software is a collection of computer
programs and related data that provide the instructions for telling a computer
what to do and how to do it.
Network: A network consists of two or more computers connected together
so they can exchange information.
Local Area Network (LAN): A Local Area Network consists of two or
more computers connected together in a building or home using physical
wire or wireless.
Wide Area Network (WAN): A Wide Area Network is a network that spans
a large geographical area, the most common example being the Internet.
Internet: The Internet, sometimes called simply The Net, is a worldwide
system of computer networks. A network of networks in which users at any
one computer can (if they have permission) get information from any other
computer.
Intranet: Intranet is the generic term for a collection of private computer
networks within an organization.

Software Development Life Cycle

(SDLC)/Software Testing Life Cycle:
SDLC: Software Development Life Cycle (SDLC) is the process or life
cycle of developing a software. Software needs to go through various
phases before it is ready for end users.
SDLC has six (6) phases.
1. Requirement Analysis
2. Design
3. Coding/Building
4. Testing
5. Deployment
6. Maintenance.
Requirement Analysis:
1. Business Requirement Documents (BRD)
2. Functional Requirement Documents/Specification (FRD/FRS)
Business Requirement Documents (BRD): BRD stands for Business
Requirement Document. It contains all the business requirements of the
users/customers. The requirements given by the end users or customers are
collected into a single document called as BRD document.
Functional Requirement Documents/Specification (FRD/FRS): FRD/FRS
has all the functional requirements that the application must have or how the
application should behave. FRD/FRS is prepared by BA, Architect and
Project Lead.

Software Testing Life Cycle (STLC): Software Testing Life Cycle (STLC)
starts from creating Test Plan, Developing Test Cases, Test Environment and
Test Data Setup, Executing Test Cases and Logging Defects and provide
Signoff.
Test Plan is details document describe how the testing will be conduct.
Test Plan contains testing tools selection, time estimation, resource
allocation, training requirements and milestone etc.
In Development Stage QA Analyst prepares Test Cases, Collect Test Data
and Requirement Traceability Matrix (RTM).
In Environment Setup Stage QA Analyst setup test data.
In Test Execution/Log Defect Stage QA Analyst execute test cases and enter
defects, verify fixed defects, provide daily testing status report.
In Signoff Stage QA Analyst provide signoff on test completion.
QA Analysts responsibilities in SDLC:
Requirement Analysis: Review requirements and provide feedback and
ensure requirements are testable.

Development Methodologies:
There are many Software Development Methodologies exist, few of them
are: Waterfall, Iterative, V-Model, Agile and Test Driven Development
(TDD).
Waterfall: Waterfall is top down approach which starts from requirement
analysis, design, coding, testing, deployment, and maintenance.
There are many advantage and disadvantages in Waterfall method, few of
them are:
Advantages:
Being a linear model, it is very simple to implement.
Documentation is produced at every stage of the softwares
development.
The amount of resources required to implement this model are
minimal.
Requirements are remain static.
Disadvantages:
Cannot go back a step; if the design phase has gone wrong, things can
get very complicated in the implementation phase.
Time consuming.
Until previous phase is complete, cannot proceed to next phase.
Doesnt support Requirement change.

Agile Advance:
Sprint Cycle starts with Sprint Planning meeting followed by Daily
Scrum/Standup, Sprint Development, Sprint Review/Showcase and Sprint
Retrospective.
At the beginning of the sprint cycle (every 3 weeks), a Sprint
planning/Analysis Meeting is held. Select what work needs to be done
(define Scope), Resource Allocation, Identify and communicate how much
of the work is likely to be done during the current Sprint.
In Sprint Planning Meeting QA Analyst review the Stories, provide
feedback, ask question if stories are ambiguous and ensure the stories are
testable.
A Stand-Up Meeting (or simply stand- up) is daily team meeting held to
provide a status update to the team members.
In Stand-Up generally three (3) questions asked:
1. What did you do since last daily Scrum?
2. What will you do until the next one?
3. What obstacle do you have?

Test Plan:
Test Plan is a document that describes how the testing will be conducted.
Test Plan also describes the scope, approach, resources and schedule of
testing. It identifies test items, features to be tested, testing tasks and any
risks requiring contingency planning.
Test Plan can be written during the requirement phase.
A Project can have only one (1) Test Plan.
QA Analysts responsibility to write Test Plan.
Before start testing, test cased development should be completed and
reviewed.

All test cases must be executed, open defects must be retested/closed and
regression testing must be completed.
Content of Test Plan:
1. Introduction
2. Application Details
3. Testing In Scope/Out Scope
4. Roles and Responsibilities
5. Supporting Documents
6. System Test Strategy
7. Test Schedule/Testing Cycle
8. Assumption and Dependencies
9. Test Data/ Test Environment
10.Entry/Exit Criteria
11.Glossary
Introduction section describes the summary of the entire project.
Application details describe the high level functional description of
the system.
In Scope describes what functionalities or systems need to be tested
and Out Scope describes what functionalities or systems will not be
tested.
Roles and Responsibilities describe who does what and owner of each
tasks. For example, BAs responsibility is to create/upgrade/maintain
requirement documents, QAs responsibility is to conduct the whole
testing process and provide signoff and so on.
Based on what documents testing process or test cases will be created
are described on Supporting documents section.
Test Strategies describes the testing technique and tools to be used for
testing.
Schedule describes the testing commence date and testing end date.
Any dependencies like test data creation, test environment setup are
described in Dependencies section.
Whether production data will be used for testing or mock up data will
be created to test the application are described in Test Data section.
In which environment testing will be conducted is described in Test
Environment section.

 Entrance/Exit Criteria describes how testing will start and end.

Test Cases:
Test Scenarios: Scenarios are usually different from test cases where test
cases are single step and scenarios are number of steps.
Scenarios are based on a hypothetical story to help a person think through a
complex problem or system.
Test Case: A Test Case is a set of conditions under which a tester will
determine whether software is working correctly or not.
A Test Case is usually a single step, or a sequence of steps, to test the correct
behavior/functionalities and features of an application. An expected result is
usually given.

Defect Management:
Defect/Bug/Issue:
While executing test cases, you may find actual result does not match
with expected result. This is nothing but a defect.
Defect also known as Incident, Bug, Problem or Issues.
Defect can resides anywhere in the system. When defect found on
web page or GUI, it is known as front end or GUI(Graphical User
Interface) defect. When defect found in database or on backend
service, it is known as backend defect.
All critical/major defect need to be fixed and verified before software
release to production.
While entering/logging defect QA Analyst Must need to provide:
Defect Summary
Steps to Reproduce
Test Data
Environment
Priority/Severity
Screen Shot

 Test Cycle
Build Version
Assigned To
Every defect will be identified by unique defect ID(which can be
generate by system of manually).
If there is any disagreement with Developer on defect Qa Analyst
should assist developer to reproduce the defect.
If the defect is rejected by Developer then QA Analyst should verify
the defect against BRD/FRD.
Business can make the decision to proceed to production with defect.
QA Analyst Must provide conditional signoff. In the conditional
Signoff QA Analyst Must provide the number of defects outstanding.

Application Types:
Standalone Application: Standalone application can run independently
without any network connections. No Internet is required. Can execute on
personal computer.

Testing Techniques:
There are two types testing. Frontend and Backend Testing.
Black Box Testing: Black Box Testing also known as functional testing
without knowing the internal logic or structure. For example- User is able to
add item to chart.
White Box Testing: White Box Testing is performed to validate internal code
structure.

QTP:
Automation: Software Test Automation is the process of automating the
steps of manual test cases using an automation tool or utility to shorten the
testing life cycle with respect to time.
Benefits of Automation:
Reliable
Repeatable
Programmable
Comprehensive
Reusable
Fast
Better Quality Software
Cost Reduction
Data Driven Testing
Coverage
When the Automation is Applicable?
Regression Testing Cycles are long and iterative
If the application is planned to have multiple release/builds
If it is long running application where is small enhancements/bug fixes
keeps happening
Test repeatability is required
Automation Process: Automation process starts with analyzing the manual
regression test cases and provide feedback on how many test cases can be
automated then develop the scripts, running the scripts and analyzing the
results to see if manual expected results matches with automation expected
results.

Manual Test Case executed successfully

Analyze test case and provide feedback
Confirm automation test suites for regression
Convert manual test cases to automated scripts

 Execute automated scripts

Analyze results and Signoff
Automation Tools:
QTP
Selenium
Rational Robot
Borland
Generally QA Engineer automated regression suite to reduce the testing
cycle time.