Quality Assurance
QA is the way of preventing the mistakes and defects in
manufactured products & avoiding the problems, when delivering the solutions
and services for customers.
Software quality
assurance
SQA consists of means of monitoring software engineering
processes or methods used for ensure quality. It’s very vital for a tester to
understand what the difference between Quality control & Quality Assurance
is.
The quality control measures the quality of the product. This
is a specific part of the Quality-Assurance procedure. This corrective activity
applies to particular product or deals with product. Priority or Severity will
be assigned to a concrete-bug to know the crucial of bug.
Defects:
Defect is an error and bug, in the app which is created. Programmer
while designing or building software can make mistakes & error. These
mistakes and errors mean that there’re the flaws in software. These’re called the
defects.
Priority:
It allows to developers for understand which bug’ve to be
fixed first.
Severity:
How-strongly the bug is affecting the app.
Test Scripts:
A test script is the script which is created through an
automation-tool while recording an app features.
Bug:
It’ll be called the bug, if the developer accepts your-defect.
The common confusion is about terms of that defect, bug, fault, false positive,
anomaly, failure, incident, error or mistake.
Test Case:
The test case is a documentation that includes information’s
about events, inputs and actions, or an estimated-response, to checks if a
singularity of the app is working properly. Test conditions. A condition is
needed for test a feature.
Test Data:
A test data means the input-data, which is giving for checks
the app’s feature whether it’s working rightly & not.
Test Bed:
Test bed is a platform to conducting the transparent,
rigorous, or replicable testing of the scientific theories, computational-tools,
or new technologies.
Baseline Document:
An approved-document or the review is known as a baseline
document that is Software requirement Specification, test plan.
Configuration
Management:
It involves the process used for coordinate, control or
track; code, requirements, tools, documentation, problems, change requests,
designs, compilers, libraries, patches or changes made for them, & who
makes the changes.
Verification and Validation:
It’s done by dynamic testing or other forms of the review. Validation
or Verification is not same thing, although they’re often confused. It is
static method to verifying the designs or codes. The software verification is a
human based checking of the files or documents. It’s a dynamic process to
checking & testing the actual product. The software validation always includes
executing the codes.
Walkthrough:
- It’s not a formal process and review.
- It’s led by authors.
- It is useful to the people if they’re not from the software-discipline, which’re not used to and can’t easily.
Inspection:
- It’s the most formal-review type.
- It’s led by the trained moderators.
- During the inspection of documents that’re prepared or checked thoroughly by reviewers before the meeting.
- This involves the peers for examine the products.
- Separate preparation is carried-out during which the product is examined or the defects are found.
- Defects found are the documented in a logging list and issue log.
- A formal follow up is carried out through the moderator applying the exit criteria.
Comments
Post a Comment