Scribd
Upload
15 views12 pages

Sqa Final Notes

Uploaded by

syed mujtuba
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
15 views12 pages

Sqa Final Notes

Uploaded by

syed mujtuba
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/ 12

TOPIC NO : 01

➢ TESTING:
The process of verifying and validating that a software program or application or product:

▫ Meets the business and technical requirements.


▫ Works as expected.
▫ Can be implemented with the same characteristic

Software Testing is necessary because we all make mistakes. Some of those mistakes are
unimportant, but some of them are expensive or dangerous.

➢ QUALITY:
Quality software is reasonably bug or defect free, delivered on time and within budget, meets
requirements and/or expectations, and is maintainable.

Key aspects of quality for the customer include:


•Good design – looks and style
•Good functionality – it does the job well
•Reliable – acceptable level of breakdowns or failure
•Consistency
•Durable – lasts as long as it should
•Good after sales service
•Value for money
➢ TWO VIEW OF QUALITY DEFINITION:
•Popular View: Quality is directly related to CLASS.
•Technical View: To meets Customer Level of Satisfaction within Time
Budget and Scope.

➢ RELATION BETWEEN QUALITY AND TESTING:


TESTING is the measurement of QUALITY

➢ GENERAL TERMS OF TESTING:


1. Bug: A bug is a mistake or problem in a computer program that makes it do something it
shouldn't or stops it from working properly.

2. Defect: A defect is a specific mistake in the program that makes it not do what it's supposed
to do. It can be simply defined as a variance between expected and actual. The defect is an
error found AFTER the application goes into production. It is the deviation of the customer
requirement.

Defect can be categorized into the following:


1. Wrong:

When requirements are implemented not in the right way. This defect is a variance

from the given specification. It is Wrong!

2. Missing:

A requirement of the customer that was not fulfilled. This is a variance from the

specifications, an indication that a specification was not implemented, or a

requirement of the customer was not noted correctly.

3. Extra:

A requirement incorporated into the product that was not given by the end

customer. This is always a variance from the specification, but maybe an attribute

desired by the user of the product. However, it is considered a defect because it’s a

variance from the existing requirements.

3. Error: An error is a mistake that people make when they are creating the program, which
can lead to defects or problems in the software.
4. Mistake: A mistake is something people do that is not right when they are making the
software, and it can cause errors or defects.
5. Fault: A fault is a big problem in the software's code or design that can lead to errors,
defects, or failures when the program is used.
6. Failure: A failure is when the software doesn't work correctly or doesn't do what it's
supposed to do when people use it, often because of bugs, defects, or faults.
DEFECTS LIFE CYCLE:
➢ Testing Objectives
The major objectives of Software testing are as follows:
• Finding defects
• Gaining confidence to gain the level of quality.
• To prevent defects.
• To make sure that the end result meets the business and user
requirements and Specifications.

➢ Testing Principles
There are following seven principles of testing:
1. Testing shows presence of defects
2. Exhaustive testing is impossible
3. Early testing
4. Defect clustering
5. Pesticide paradox
6. Testing is context dependent
7. Absence – of – errors fallacy

➢ Fundamental Test Process / Software Test Life Cycle


1. Planning and Control
2. Analysis and Design
3. Implementation and Execution
4. Evaluating exit criteria and Reporting
5. Test Closure activities
TOPIC NO: 02

➢ Selenium for Automation Testing


Selenium is a free and open-source test automation suite used for automating web-based
applications. It supports automation across different browsers, platforms, and
programming languages.

• Selenium Suite comprises of the following four components-


• Selenium IDE
• Selenium RC
• Selenium WebDriver
• Selenium Grid
ADVANTAGES OF SELENIUM:

• Selenium is open source, there is no licensing cost for its usage.


• Scripting can be done in most of the widely used programming languages like Java, C#,
Ruby, and Python.
• It provides platform support for all the major operating systems – Windows, Linux, Mac
OS, and Solaris.
• It supports most of the popular browsers like Chrome, Firefox, Edge, Internet Explorer,
Opera, and Safari.
• The Selenium IDE component of the Selenium suite provides record and playback
features using which non-programmers can also write automation scripts.
• Selenium Grid helps in parallel and distributed testing.

TOPIC NO: 03
➢ AGILE:
Agile is a set of values and principles that guide and shape development.
There are a number of agile development methods that embody these values
and principles in their practices:
• Extreme Programming (XP)
• Scrum
• Kanban
• Crystal Agile Framework
• Dynamic System Development Method (DSDM)
• Feature-Driven Development (FDD)

SCRUM: Scrum is a lightweight framework that helps people, teams and


organizations generate value through adaptive solutions for complex problems.
Foundation of Scrum:
Empiricism: knowledge is acquired through experience
Lean thinking: focus on the core essentials and reduce waste whenever
possible
Transparency: both the process and work artifacts must be visible
Transparency ➤ Inspection ➤ Adaptation
Scrum Values:
• Commitment
• Focus
• Openness
• Respect
• Courage

The Sprint:
The Scrum process is composed of a sequence of sprints.
• In Scrum a sprint is short –usually <1 month long (1-4 weeks)

Product Backlog:
• Includes the Product Goal – the “long-term objective” for the Scrum team
• The rest of the Product Backlog is a prioritized list of what needs to be done
to improve the software product (satisfy the Product Goal!)
• Often items in a Product Backlog are represented as user stories.
• Individual stories can also have associated story points that represent how
much work is required to complete a given story
• Items in the Backlog are regularly reviewed and refined to break them into
small more manageable items of work.

Sprint Backlog:
• The Sprint Backlog is an artifact for the current Sprint.
• It is put together by the developers and contains:
• A Sprint Goal
• A subset of Product Backlog items relevant to the Sprint Goal
• A Sprint plan for delivering an increment.

What is an Increment?
• An increment is a verified step toward achieving the Product Goal
• One or more increments per sprint that build on top of past increments
https://www.youtube.com/watch?v=gy1c4_YixCo&t=83s

You might also like