1. TESTING
ATTRIBUTES

2. Testing Methodology
 Understand requirement from
 requirement document and/or from development meetings
 Prepare work flow diagrams to
 have a visual understanding of the system (for functional testing)
 learn which related areas of product/service would be impacted
by enhancements (for integration and regression testing)
 Turn all this information into
 Test Cases/Checklist (click links below for examples)
 Testing Checklist: https://www.box.com/shared/q5kkh2rvtn
 Test Results: https://www.box.com/s/gg9vtj1xn5zr4edfnb2e
 Test Cases: https://www.box.com/s/86lmi7f2u042c3l8q9bu
 Manual Scripts for QA: https://www.box.com/s/3geutf1ueoz9g0taqw7b
 QA Testing Report: https://www.box.com/s/k360ozikh982jeqs02qg

3. Team Player - Communication
 Explain unexpected behaviour in the system
 in writing in the bug tracker with full demonstration such as
 screenshot,
 browser version,
 replication steps and error details (time of error so logs can
be checked) was always appreciated by developers
 Ask developers as to what details they need for
troubleshooting. This not only ensured quality but
also helped developers in their work

4. Fulfil pre-requisite of testing:
 Ensure that developers have conducted unit testing
before compiling a code into a release. This save
testing time in running, reporting, and repeating.
 Testing new changes on old build is counter
productive. Therefore ensured that testing is being
done on new builds by verifying version numbers.

5. Promptness
 Development Schedule (agile example)
 Coding Time = Monday - Friday
 Code freeze = Friday
 Testing start = Tuesday – Friday
 Live date= Monday noon
 Testing Schedule
 Report bugs right away to shorten the time between work and
rework.
 Test/retest all bugs by Friday.
 Close/Verify remaining on Monday before release time.
Following this schedule the releases were live on
schedule allowing to meet final launch time.

6. Technical Skills
 MS Office
 Testing tools
 QTP
 Loadrunner
 Open defect count & Defect Density
 Defect Density = Total no of defects / Total no of test
Cases
 The lower the number the better
 Open defect count:
 count defect per day or per week.
 If open defect count is more means there is problem in
defect fixing, or there are more new bugs found as testing
is done.

7. Passion
 Software testing is exciting! is the attitude
for this field or any field.
 A common question asked is if QA is Boring
 Software Testing requires making sense of
Business Requirements and draft test cases
based on your understanding. What is boring is
doing the same set of tasks repeatedly. The key
is to try new things.

8. Great Attitude
 Test to break
 Testing of sigin feature – from facebook, newlestters, website etc
 Detail orientation
 Understand requirements via development meetings and
preparing flow diagrams. This ensures that each related aspect
of new feature or modification is tested.
 Willingness to learn
 Learned to update server with new build. This saved developer’s
time and gave more control on testing environment
 Suggest process improvements
 Maintain a log of customer care feedback and used in product
development meetings.
 Tested from from every
 end user point of view to suggest improvements.

9. Independent
 Take ownership of the task and complete it without
much direct supervision.
 Example:
 Prepared test cases, conducted testing, testing
reports and followed open tickets/bugs to conclusion.
 Learned updating servers using automated scripts
written by programmers.

10. Typical Workday:
 understanding requirement documents,
 creating test cases ,
 executing test cases ,
 reporting and re-testing bugs ,
 attending review meetings and other team building
activities.

11. Generate revenue and
maintain client loyalty
 Developers on a team are sometimes on budget but
management should allow testers test bug fixes and
new features several hours a week even though the
project plan have them only working two weeks at
the end. The projects will still be profitable and
customers get a better product because of it
 Related stories to share:
 Invoice collection on projects e.g, atrium, bws and jsr.
 Identified flaw in CC processing – saving monetary flow.

12. Career Goals
 QA Analyst (current) >>
 Sr. QA Analyst (2-3 year)>>
 QA Team Coordinator (5-6 year)>>
 Test Manager (8-11 year)>>
 Senior Test Manager (14+)
In parallel get ISTQB certified and other industry
related certifications.