|
Tool Expertise
|
Automated functional and regression testing - WinRunner, QuickTest,
QA Center, RationalRobot
|
|
Load Testing - LoadRunner, WebLoad, QA Load, SilkPerformer
|
|
Defect and Change Tracking - Test Director, ClearQuest, Bugzilla,
GNATS, TeamTrack
|
|
Configuration Management - CVS, VSS, PVCS, SVN, Source Jammer
and Perforce, Endeavor
|
|
Opensource tool - OpenSTA
|
|
Bug Tracking - Bugzilla, JIRA, TeamTrack and Mantis
|
|
Configuration Management Tools - VSS, CVS
|
|
|
Software Life Cycle
|
|
The life cycle begins when an application is first conceived and ends when it is
no longer in use.
|
|
It includes aspects such as:
|
|
Initial concept
|
|
Requirements analysis
|
|
Functional design, Internal design
|
|
Documentation planning
|
|
Test planning
|
|
Coding
|
|
Document preparation, Integration
|
|
Testing
|
|
Maintenance, updates, retesting, phase-out, and other aspects
|
|
|
Quality Assurance in the
Software Life Cycle
|
|
|
|
Software Testing
|
|
"Software Testing" involves operation of a system
or application under controlled conditions and evaluating the results (eg, “if the
user is in interface A of the application while using hardware B, and does C, then
D should happen”).
The controlled conditions should include both normal and abnormal conditions. Testing
should intentionally attempt to make things go wrong to determine if things happen
when they shouldn't or things don't happen when they should.
It is oriented to “detection”.
|
|
|
|
Verification
|
|
"Verification" typically involves reviews and meetings
to evaluate documents, plans, code, requirements, and specifications.
This can be done with checklists, issues lists, walkthroughs, and inspection meetings.
|
|
Validation
|
|
"Validation" typically involves actual testing and
takes place after verifications are completed.
The term “IV & V” refers to Independent Verification and Validation.
|
|
Walkthrough
|
|
A “walkthrough” is an informal meeting for evaluation
or informational purposes.
Little or no preparation is usually required.
|
|
Inspection
|
|
An "Inspection" is more formalized than a “walkthrough.”
The subject of the inspection is typically a document such as a requirements spec
or a test plan, and the purpose is to find problems and see what's missing, not
to fix anything. Attendees should prepare for this type of meeting by reading through
the document; most problems will be found during this preparation.
The result of the inspection meeting should be a written report. Thorough preparation
for inspections is difficult, painstaking work, but is one of the most cost effective
methods of ensuring quality.
|
|
The following is a short
list of quality assurance principles:
|
|
Test and QA activities start early in the software development life cycle.
|
|
Quality is built into the solution: “Do it right the first time".
|
|
Each step or phase is validated before moving ahead to the next step or phase.
|
|
Repeatable processes are established and used by all like projects.
|
|
Processes are continuously reviewed and improved.
|
|
|
SentientIT promises a compelling experience
that will generate new and greater revenue opportunities, increasing customer loyalty
and hence gaining competitive advantages for your organization.
|