Scribd
Upload
393 views5 pages

Why Most of The Software Company Preferred Manual Testing Even Though Many Automation Testing Tools Are Present in The Market

The document discusses various testing concepts and terms including reasons for manual testing over automation, types of test coverage and CMM levels, the software testing process, definitions of build and build configuration, entry and exit criteria, types of metrics in testing, independent testing, and differences between types of testing. It also addresses test matrices, gap analysis, differences in test cases based on test type, definitions of test case levels and contents, deferred testing, and risk analysis including types of risks.

Uploaded by

Rajesh Reddy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
393 views5 pages

Why Most of The Software Company Preferred Manual Testing Even Though Many Automation Testing Tools Are Present in The Market

The document discusses various testing concepts and terms including reasons for manual testing over automation, types of test coverage and CMM levels, the software testing process, definitions of build and build configuration, entry and exit criteria, types of metrics in testing, independent testing, and differences between types of testing. It also addresses test matrices, gap analysis, differences in test cases based on test type, definitions of test case levels and contents, deferred testing, and risk analysis including types of risks.

Uploaded by

Rajesh Reddy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

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?

Answers:
1. 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)

2. Test coverages are of two types. They are-

 Features to be tested:The list of all the features within the test engineer’s scope.
 Features not to be tested:The list of all the features beyond the test engineer’s scope.

Ex: low rik areas,skipping some functionalities based on the time constraints.

3. CMM Levels Explanation

4. Just follow STLC process: Test Initiation, Test Planning, Test Design, Test Execution, Test
Reporting & Test Closure.

5. In a programming context, a build is a version of a program. As a rule, a build is a pre-release


version and as such is identified by a build number, rather than by a release number. Reiterative
(repeated) builds are an important part of the development process. Throughout development,
application components are collected and repeatedly compiled for testing purposes, to ensure a
reliable final Product. Build tools, such as make or Ant, enable developers to automate some
programming tasks.

As a verb, to build can mean either to write code or to put individual coded components of a
program together.

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

7. In testing there are two types of metrics.

 Process metrics
 Product metrics

Process Metric: A metric used to measure the characteristic of the methods,technique, and tools
employed in developing,imlementing,and maintaining the software system.

Product Metric: Metric used to measure the characteristic of the documentation and code.

8. Testing by individuals other than those involved in the development of the product or system

IVY Interview Questions


1. Tell me about yourself?
2. Your current project architecture.
3. What is white box & black box?Diff b/w them?
4. How QTP recognizes the Objects?
5. What if the object properties change compared to Recording?Run fails?
6. Given a simple election Application form and asked to write min number of functional
Test cases to cover the whole form functionality?
7. Why automation?What do you get from it?
8. How to reduce the project budget?
9. When we need to go for descriptive programming in QTP?

 1. What is the process followed in your company?

 2. Difference btw black Box and white Box Testing ?

 3. Difference btw Alpha and Beta Testing ?

 4. What is mean by Static and Dynamic Testing ?

 5. What are the techniques you’ll be using while testing a single textbox of login page ?

 6. How u’ll track whether all your client requirements are covered in your testing. Is there
any specific procedure followed in your company ?

 7. Are you aware of Test Director ?

 8. Explain the scenario where you have struggled to find the bug ?

 9. Tell me a bug which you u have find in a very different way that noone will be
followed.

What Should be Done if you Don’t Have Enough Time for Testing?

Since it’s rarely possible to Test every possible aspect of an Application, every possible
combination of events, every dependency, or everything that could go wrong, risk analysis is
appropriate to most software development projects. This requires judgement skills, common
sense, and experience. (If warranted, formal methods are also available.) Considerations can
include:

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?

Client will also contribute some ideas to utilize the available time. All this depends on
organization to organization and person to person.

What are the key challenges of testing?


1.       Requirements are not freeze.
2.       Application is not testable.
3.       Tester & Developer communication is not happening
4.       Defect in defect tracking system
5.       Miscommunication or no Communication
6.       Bug in software development tools.
7.       Proper decision making and team management
8.       Time pressures
9.       Lack of resources
10.   Lack of tools
11.   Lack of training

Difference between Functional and Non-functional Testings?


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

Functional Testing
Non-Functional Testing

Functional testing is concentrating on customer requirements and the Non-Functional testing is


concentrating on customer expectations.

What are the Common Factors in Deciding When to Stop Testing?

Common factors in deciding when to stop Testing:

1. Show stoppers encountered


2. Too many minor bugs pending to be fixed
3. Deadlines (release deadlines, testing deadlines, etc.)
4. Test cases completed with certain percentage passed
5. Test budget depleted
6. Coverage of code/functionality/requirements reaches a specified point
7. Bug rate falls below a certain level
8. Beta or alpha testing period ends

All this depends and varies from organization to organization. But these are the general factors to
take into consideration. If you want to add anything, let us know by making a comment below.

You might also like