• Should have 4-7 years experience

• Knowledge of HP products – Quick Test Pro, Quality Center

• Knowledge of database design and interrogation using SQL 2005
• Knowledge of Development Languages like JAVA2 – Visual Basic.Net etc.
• Exposure to testing best practices and processes, knowledge of various testing techniques
• Experience of developing and deploying test environments
• Knowledge of object oriented analysis and design techniques using UML
• Understanding of system architectures including client, client-server, Web based
• Understanding of Web based Application testing essential
• Experience of automated testing (e.g. VSTS experience would be the preferred tool) and
maintenance of automated test suites is essential
• Config Management / Version Control (Quality Center/Accurev/CVS/VSS) effectively to
manage automation scripts/scenarios
• Exposure to Iterative-Incremental delivery models like Agile or Scrum
• QA Certifications – CSTE, ISTQB

SDLC (Software Development Life Cycle)

Models
Posted on March 05th, 2009 in Manual Testing
After accepting a software proposal, the corresponding project managers should one of the
available 5 sdlc model to follow in the development cycle.
There are 5 SDLC models available currently.They are
1. Waterfall Model
2. Prototype Model
3. Incremental Model
4. Spiral Model
5. V-Model
Waterfall Model: When the customer requirements are clear and complete
Requirements Gathering—>Analysis & Planning—> Design—> Coding—> Testing—> Release
& Maintenance
Prototype Model: When the customer requirements are unclear and confusing
Incremental Model: When the customer requirements are clear but not complete, because client
is giving requirements in installment basis.
Spiral Model: When the customer requirements are clear and complete but enhancing in future
Note: In above 4 SDLC models the testing is available as one stage and the stage was also
conducted by same developers.Due to this the organizations are concentrating on multiple stages
of testing and separate testing teams for quality software development.
UNIT testing is the first testing stage in software development. Validating each and
every line of code in programs is called unit testing. All the single programs in
software should under go unit testing to ensure that each and every single program
is working fine independently.

Error Guessing is a case design technique where the tester has to guess what faults might occur
and to design the tests to represent them.
Error Seeding is the process of adding known faults intentionally in a program for the reason of
monitoring the rate of detection & removal. And also to estimate the number of faults remaining
in the program.

If the client/customer/end user finds a defect while using the released application.Then it is
called as Defect Leakage or bug leakage.
OR in other words
After the release of the application to the client, if the end user gets any type of defects by using
that application then it is called as Defect leakage. This Defect Leakage is also called as Bug
Leak.
Testing the application with customer expected load in customer expected
environment is called Load Testing.

Testing the application with customer expected load in customer expected environment
continuously until the application breaks/crashes is called Stress Testing.
In simple words we can say: Load test doing continuously to find the system is called Stress
testing.
Here are some reason why companies choose manual testing initially
• Automation tools have some limitation
• Tools can’t test 100% of the application features
• Automation is too costly
• Automation needs skilled persons, which makes companies again to spend much money
• Tools are very costly (Ex: QTP costs 6 lack per each licence)
6. Entry criteria:
• All source codes are unit tested
• All QA resource has enough functional knowledge
• H/W and s/w are in place
• Test plans and test cases are reviewed and signed off
Exit criteria:
• No defect over a perod of time or testing effort
• Planned deliverables are ready
• High severity defects are fixed

1. Why most of the software company preferred Manual testing even though many
automation testing tools are present in the market?
 2. What is test Coverage?
3. What are the Type of CMM Levels, Explain Each Level.
4. How do you go about testing a project? in Manual testing?
5. what is build? what is build configuration?
6. What is Entry Criteria & Exit Criteria.
7. What type of metrics we prepare in testing?
8. What is Independent Testing?
9. what is the difference between system integrated testing and integrated system testing and
Manual Testing?
10. Please explain test matrices?
11. What is Gap Analysis?. Is there any template for it.Describe briefly about Gap Analysis
Please?
12. Do the test cases differ for Functional, Integration, System and User Acceptance Testing?
13. What is the clear meaning of test case, levels in test case ? contents of test case.
14. Could any body tell me about ‘Deferred test’?,please. when will we use ‘Deferred test’?
Who will use it?
15. What is Risk Analysis? Types of risks?

Localization Testing: Localization is the process of customizing a software Application

that was originally designed for a domestic market so that it can be released in foreign
markets. This process involves translating all native language strings to the target
language and customizing the GUI so that it is appropriate for the target market.
Depending on the size and complexity of the software, localization can range from a
simple process involving a small team of translators, linguists, desktop publishers and
engineers to a complex process requiring a Localization Project Manager directing a team
of a hundred specialists. Localization is usually done using some combination of in-house
resources, independent contractors and full-scope services of a localization company.
Globalization Testing: The goal of globalization testing is to detect potential problems in
Application design that could inhibit globalization. It makes sure that the code can handle all
international support without breaking functionality that would cause either data loss or display
problems.
Globalization testing checks proper functionality of the product with any of the culture/locale
settings using every type of international input possible. Proper functionality of the product
assumes both a stable component that works according to design specification, regardless of
international environment settings or cultures/locales, and the correct representation of data.
Automated testing offers the following advantages that are not offered by Manual testing:
1. Reusability: The tests that you automate can be reused during different phases of the
testing process.
2. Consistency: Automated tests provide the same Test Result every time. Therefore, you
use automated tests for regression testing.
3. Productivity: Automated testing enables you to run tests unattended. Therefore,human
resources that are otherwise involved in the testing process can be used for accomplishing
other tasks and the overall testing productivity of your organization increases.
Test Strategy: Test Strategy defines an approach to be followed by testing team n current
project.
Test Strategy is a organization level document which is common for all the projects in the
organization with small customizations. It will explain the process you will follow in the current
project to the out side world or clients.
System testing:
After completion of software Integration and integration testing, the development team is
releasing a software build to test engineer team.
The testing team is conducting system testing on that software in two sub levels such as
1. Functional Testing
2. Non-Functional Testing
Functional testing is concentrating on customer requirements and the Non-Functional testing is
concentrating on customer expectations.
Functional Testing: It’s a mandatory testing level, during this test the testing team is validating
a software build functionality in terms of below factors with respect to customer requirements.
1. Behavioral / GUI: The changes in properties of objects OR controls in a software is
called behavioral or GUI.
2. Input Domain: Whether the objects are taking correct type and size of inputs or not?
3. Error Handling: Whether our software is preventing wrong operations or not?
4. Manipulations: Whether our software is generating correct output or not?
5. Database Validity: Whether our software front end screens operations are correctly
impacting on database of the software or not?
6. Sanitation: Finding extra operations in a software with respect to customer requirements.
The above factors checking on a software is called as functional testing. During this checking the
testers are using black box testing
Non-Functional Testing: After completion of functional testing successfully, the
testing team is concentrating on non-functional testing. During non-functional
testing, the testing team is concentrating on customer expectations or software
characteristics.
What Should be Done if you Don’t Have Enough Time for Testing?
1. Use risk analysis to determine where testing should be focused.
2. Which functionality is most important to the project’s intended purpose?
3. Which functionality is most visible to the user?
4. Which functionality has the largest safety impact?
5. Which functionality has the largest financial impact on users?
6. Which aspects of the application are most important to the customer?
7. Which aspects of the application can be tested early in the development cycle?
8. Which parts of the code are most complex, and thus most subject to errors?
9. Which parts of the application were developed in rush or panic mode?
10. Which aspects of similar/related previous projects caused problems?
11. Which aspects of similar/related previous projects had large maintenance expenses?
12. Which parts of the requirements and design are unclear or poorly thought out?
13. What do the developers think are the highest-risk aspects of the application?
14. What kinds of problems would cause the worst publicity?
15. What kinds of problems would cause the most customer service complaints?
16. What kinds of tests could easily cover multiple functionalities?
 17. Which tests will have the best high-risk-coverage to time-required ratio?

Desired Profile
• Designing and developing database objects in Oracle 9i/10g
• Developing PL/SQL code
• Writing Database triggers Developing interfaces using Developer Forms
• Excellent English communication skills (written / spoken)