Tell me about yourself :

Hi My Self Hemanth Kumar Reddy

I have completed my Graduation from JNTUA
Currently working for
I am having 4 years of Experience which is into Functional Testing

Currently working for the Project FXR,

Here my role is Functional Tester and my responsibilities are:

 Analyzing functional requirements and translate them to test cases.

 Ensuring all Test scenarios/Test Cases are reviewed by Business Analyst and Review
Incorporation.
 Review and Maintenance test cases/Requirements/Screen shots and test results using JIRA &
iSolve tool.
 Test Case Preparation and Execution & Test Data Preparation
 Experienced in performing Integration, System, Regression UAT and GUI Functional testing.
 Testing in the Application was conducted with the Knowledge of Insurance Domain.
 Involved in Defect analysis and retesting the same.
 Co-ordination with different benzene level leads to meet requirements.
 Customer & Onsite co-ordination to understand the issues and resolve.
 Time Management in the term of Attending Scheduled Client Meeting and No slippage in the
Delivery time line.
 Running SQL queries in Oracle SQL Server12c to fetch the data.
 Performing Sanity/Smoke/SIT/UAT based and Regression testing for the defects logged.
 Delivery of Daily Dashboard Test Reports (Daily Status Report) through Excel to Stake Holders of
the Project.

1. What is functional system testing?

Testing the end to end functionality of the system as a whole is defined as a functional system
testing.

2. What is the Basis path testing?

A testing mechanism proposed by McCabe.

Aim is to derive a logical complexity measure of a procedural design and use this as a
guide for defining a basic set of execution paths.
Test cases which exercise basic set will execute every statement at least once.

3. What is Black Box Testing?

Focus on functional requirements.

 Compliments white box testing.

Attempts to find:

 incorrect or missing functions

 interface errors
 errors in data structures or external database access
 performance errors
 initialization and termination errors.

4. What is Equivalence Partitioning?

Divide the input domain into classes of data for which test cases can be generated.

Attempting to uncover classes of errors.

Based on equivalence classes for input conditions.

An equivalence class represents a set of valid or invalid states

An input condition is either a specific numeric value, range of values, a set of related values, or
a boolean condition.

Equivalence classes can be defined by:

 If an input condition specifies a range or a specific value, one valid and two
invalid equivalence classes defined.
 If an input condition specifies a boolean or a member of a set, one valid and one
invalid equivalence classes defined.

Test cases for each input domain data item developed and executed.

5. What is Boundary Value Analysis.

Large number of errors tend to occur at boundaries of the input domain.

BVA leads to selection of test cases that exercise boundary values.

BVA complements equivalence partitioning. Rather than select any element in an

equivalence class, select those at the ''edge' of the class.

Examples:

 For a range of values bounded by a and b, test (a-1), a, (a+1), (b-1), b, (b+1).
 If input conditions specify a number of values n, test with (n-1), n and (n+1)
input values.
 Apply 1 and 2 to output conditions (e.g., generate table of minimum and
maximum size).
 If internal program data structures have boundaries (e.g., buffer size, table
limits), use input data to exercise structures on boundaries.

6. What are Cause Effect Graphing Techniques.

Translation of natural language descriptions of procedures to software based algorithms is

error prone.
Example: From US Army Corps of Engineers:

Executive Order 10358 provides in the case of an employee whose work week varies from
the normal Monday through Friday work week, that Labor Day and Thanksgiving Day each
were to be observed on the next succeeding workday when the holiday fell on a day outside
the employee's regular basic work week. Now, when Labor Day, Thanksgiving Day or any of
the new Monday holidays are outside an employee's basic workbook, the immediately
preceding workday will be his holiday when the non-workday on which the holiday falls is
the second non-workday or the non-workday designated as the employee's day off in lieu of
Saturday.
When the non-workday on which the holiday falls is the first non-workday or the non-workday
designated as the employee's day off in lieu of Sunday, the holiday observance is moved to the
next succeeding workday.

7. How do you test code which attempts to implement this?

Cause-effect graphing attempts to provide a concise representation of logical combinations and

corresponding actions.

 Causes (input conditions) and effects (actions) are listed for a module and an identifier
is assigned to each.
 A cause-effect graph developed.
 Graph converted to a decision table.
 Decision table rules are converted to test cases.

8. Tell me about Error Handling:

 Error description unintelligible

 Error noted does not correspond to error encountered
 Error condition handled by system run-time before error handler gets control.
 Exception condition processing incorrect
 Error description does not provide sufficient information to assist in determining error.

9. What is Integration Testing

Can attempt non-incremental integration - putting everything together at once and

test as a whole.
Usually a disaster. Incremental Testing - integrate and test in small doses
 10. Enlist some important test scenarios for testing a website.

Answer: There are many parameters that should be considered while deciding the important
test scenarios for testing any website. Also, the type of website to be tested and its
requirement specification plays an important role here.
Enlisted below are few important test scenarios that are applicable for testing any type of
website:
 Test the GUI (Graphical User Interface) of the website for verifying the
consistency of the design elements and page layout.
 All page links and hyperlinks are checked for their redirection to the
desired page.
 In case of presence of any forms or fields on the website, testing scenarios
consist of testing with valid data, invalid data, testing with existing records as
well as testing with empty records.
 Functionality testing as per the requirement specification is done.
 The performance of a website is tested under heavy loads to determine the
web server response time and database query time.
 Compatibility testing is done to test the behavior of an application on a
different browser and OS (operating system) combinations.
 Usability testing and Database testing is also performed as a part of
test scenarios.

11. Bottom Up Integration.

Begin construction and testing with atomic modules (lowest level modules).

Use driver program to test.

Steps:

 Low level modules combined in clusters (builds) that perform specific

software subfunctions.
 Driver program developed to test.
 Cluster is tested.
 Driver programs removed and clusters combined, moving upwards in
program structure.
12. What is Alpha and Beta Testing

Difficult to anticipate how users will really use software.

If there is one customer, a series of acceptance tests are conducted (by the customer) to
enable the customer to validate all requirements.
If software is being developed for use by many customers, can not use acceptance
testing. An alternative is to use alpha and beta testing to uncover errors.
Alpha testing is conducted at the developer's site by a customer. The customer uses
the software with the developer 'looking over the shoulder' and recording errors and
usage problems. Alpha testing conducted in a controlled environment.
Beta testing is conducted at one or more customer sites by end users. It is 'live' testing in
an environment not controlled by the developer. The customer records and reports
difficulties and errors at regular intervals.

13. What is Security Testing

Systems with sensitive information or which have the potential to harm individuals
can be a target for improper or illegal use. This can include:
• attempted penetration of the system by 'outside' individuals for fun or
personal gain.
• disgruntled or dishonest employees
During security testing the tester plays the role of the individual trying to penetrate the
system. Large range of methods:
• attempt to acquire passwords through external clerical means
• use custom software to attack the system
• overwhelm the system with requests
• cause system errors and attempt to penetrate the system during recovery
• browse through insecure data.

14. What is Stress Testing

Stress testing is designed to test the software with abnormal situations. Stress
testing attempts to find the limits at which the system will fail through abnormal
quantity or frequency of inputs. For example:
• Higher rates of interrupts
• Data rates an order of magnitude above 'normal'
 • Test cases that require maximum memory or other resources.
• Test cases that cause 'thrashing' in a virtual operating system.
• Test cases that cause excessive 'hunting' for data on disk systems.
Can also attempt sensitivity testing to determine if particular combinations of otherwise
normal inputs can cause improper processing.

15. What is Performance Testing

For real-time and embedded systems, functional requirements may be satisfied but
performance problems make the system unacceptable.
Performance testing checks the run-time performance in the context of the integrated
system.
Can be coupled with stress testing.
May require special software instrumentation.

16. What is Debugging.

Debugging is not testing.

Debugging occurs because of successful testing.
Less well 'understood' than software development.
Difficulties include:
Symptom and cause may be 'geographically' remote. Large problem in highly coupled
software structures.
• Symptoms may disappear (temporarily) and another error is corrected.
• Symptom may not be caused by an error (but for example, a
hardware limitation).
• Symptom may be due to human error.
• Symptom may be due to a timing problem rather than processing problem.
• May be hard to reproduce input conditions (especially in real-time systems)
• Symptom may be intermittent - especially in embedded
systems. Not everyone is good at debugging.
 17. What different types of manual testing are there?

Different types of manual testing are;

Black Box Testing

White Box Testing
Unit Testing
System Testing
Integration Testing
Acceptance Testing.

18. What is risk-based testing?

Risk-based Testing is the term used for an approach to creating a Test Strategy that is based
on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and
prioritizing of risks by risk level. Tests to address each risk are then specified, starting with
the highest risk first.

19. What is API testing?

API testing is a type of software testing where application programming interfaces

(APIs) are tested to determine if they meet expectations for functionality, reliability,
performance, and security. In simple terms, API testing is intended to reveal bugs,
inconsistencies or deviations from the expected behavior of an API.

20. What’s the difference between verification and validation in testing?

Verification: It is a static analysis technique. Here, testing is done without executing the
code. Examples include – Reviews, Inspection, and walkthrough
Validation: It is a dynamic analysis technique where testing is done by executing the
code. Examples include functional and non-functional testing techniques.
 21. Explain how to test documents in a project that span across the software
development lifecycle?

The project span across the software development lifecycle in the following manner

 Central/Project test plan: It is the main test plan that outlines the complete test
strategy of the project. This plan is used till the end of the software development
lifecycle
 Acceptance test plan: This document begins during the requirement phase and is
completed at the final delivery
 System test plan: This plan starts during the design plan and proceeds until the end
of the project
 Integration and Unit test plan: Both these test plans start during the execution phase
and last until the final delivery

22. How can you eliminate the product risk in your project?

It helps you to eliminate product risk in your project, and there is a simple yet crucial step
that can reduce the product risk in your project.

 Investigate the specification documents

 Have discussions about the project with all stakeholders including the developer
 As a real user walk around the website

23. What are the different configurations that have to be considered while
testing a website?

Answer: Different configuration includes different browsers as well as an operating system on

which a website is being tested. Browser plugins, text size, video resolution, color depth,
browser setting options are also considered when we talk about configurations.
Different combinations of browsers and operating systems are used to test the compatibility
of the website. Usually, the latest and the last latest versions are included. Well, these
versions are usually specified in the Requirement document.

Few important browsers include:

 Internet Explorer
 Firefox
 Chrome
 Safari
  Opera
Few important Operating systems include:
 Windows
 UNIX
 LINUX
 MAC

24. What are the phases involved in Software Testing Life Cycle?

The different phases involved in the software testing life cycle are:

Phases Explanation

QA team understands the requirement in terms of what we

Requirement Analysis
will testing & figure out the testable requirements.

In this phase, the test strategy is defined. Objective & the scope
Test Planning
of the project is determined.

Here, detailed test cases are defined and developed. The

Test Case Development
testing team also prepares the test data for testing.

It is a setup of software and hardware for the testing teams to

Test Environment Setup
execute test cases.

It is the process of executing the code and comparing the

Test Execution
expected and actual results.

It involves calling out the testing team member meeting &

Test Cycle Closure evaluating cycle completion criteria based on test coverage,
quality, cost, time, critical business objectives, and software.

25. What do you understand by Server-side validation?

Answer: Server-side validation occurs where the validation and processing of user
requests require the response from the server. To understand it more clearly, the user’s
input is being sent to the server and validation is done using server-side scripting
languages such as PHP, Asp.NET, etc.
After the validation process, feedback is sent back to the client in the form of a
dynamically generated web page.
When compared to the Client-Side validation process, the Server-side validation process is
more secure because here application is protected against malicious attacks and users can
easily bypass client-side scripting language.

26. A Type of Functional Testing, which investigates the functions relating to

the detection of threats, such as virus from malicious outsiders?

Ans. Security Testing

27. Testing activity which is performed to expose defects in the interfaces and in
the interaction between integrated components is?

Ans. Integration Level Testing

28. Could reviews or inspections be considered part of testing?

Ans. Yes, because both help detects faults and improves quality.

29. Why does the boundary value analysis provide good test cases?

Ans. Because errors are frequently made during programming of the different cases near the
'edges' of the range of values.