Hewitt associates interview questions manual testing

Static testing is a kind of testing for reviewing the work products or documentation that are being created throughout the entire project. It allows reviewing the specifications, business requirements, documentation, processes and functional requirements in the initial phase of testing. So that the testers involved in it can understand the requirements in more detail before starting the testing lifecycle which intends to help in delivering the quality product.

What is Dynamic Testing? Testing performed by executing or running the application under test either manually or using automation. Explain the different types of specification-based test design techniques? Specification-based test design techniques are also referred to as black-box testing. It involves testing based on the specification of the system under test without knowing its internal architecture.

The different types of specification-based test design or black box testing techniques are-. Explain equivalence class partitioning. Equivalence class partitioning is a specification-based black-box testing technique. In equivalence class partitioning, a set of input data that defines different test conditions are partitioned into logically similar groups such that using even a single test data from the group for testing can be considered as similar to using all the other data in that group.

For example, for testing a Square program a program that prints the square of a number , the equivalence classes can be- Set of Negative numbers, whole numbers, decimal numbers, set of large numbers, etc. What is boundary value analysis? Boundary value analysis is a software testing technique for designing test cases wherein the boundary values of the classes of the equivalence class partitioning are taken as input to the test cases e.

What is decision table testing? Decision tables are particularly helpful in designing test cases for complex business scenarios involving verification of application with multiple combinations of input. What is a cause-effect graph? A cause-effect graph testing is a black-box test design technique in which graphical representation of input i. What is state transition testing? State transition testing is a black box test design technique based on a state machine model. State transition testing is based on the concept that a system can be defined as a collection of multiple states and the transition from one state to another happens because of some event.

What is the use case testing? A use case testing is a black-box testing approach in which testing is carried out using use cases. A use case scenario is seen as an interaction between the application and actors users. These use cases are used for depicting requirements and hence can also serve as a basis for acceptance testing.

What is Test Coverage? It is a metric that measures the amount of testing performed on software while executing the test cases. Test coverage for any software can be calculated as the percentage of the number of test areas or coverage items covered with respect to the total number of test areas. The higher the test coverage, the more the part of the software gets covered by test cases and hence, the more effective will be the testing.

What is structure-based testing? Structure-based test design techniques are also referred to as white box testing. In these techniques, the knowledge of code or internal architecture of the system is required to carry out the testing.

The various kinds of testing structure-based or white testing techniques are-. What is code coverage? Code coverage is the measure of the amount of code covered by the test scripts. It gives the idea of the part of the application covered by the test suite. What are Statement testing and statement coverage in white box testing? Statement testing is a white box testing approach in which test scripts are designed to execute code statements.

Statement coverage is the measure of the percentage of statements of code executed by the test scripts out of the total code statements in the application. The statement coverage is the least preferred metric for checking test coverage.

What is decision testing or branch testing? Decision testing or branch testing is a white box testing approach in which test coverage is measured by the percentage of decision points e. What are the different levels of testing? Testing can be performed at different levels during the development process.

Performing testing activities at multiple levels helps in the early identification of bugs. The different levels of testing are —. What is unit testing? Unit testing is the first level of testing and it involves testing individual modules of the software.

It is usually performed by developers. What is integration testing? Integration testing is performed after unit testing. In integration testing, we test the group of related modules. It aims at finding interfacing issues between the modules. What are the different types of integration testing? The different type of integration testing is-. For details check Integration testing. What is a stub? In those cases, Stubs or dummy modules are used that simulate the working of modules by providing a hard-coded or expected output based on the input values.

What is a driver? In the case of bottom-up integration testing, drivers are used to simulating the working of top-level modules in order to test the related modules lower in the hierarchy. What is system testing? System testing is the level of testing where the complete software is tested as a whole. The conformance of the application with its business requirements is checked in system testing.

What is acceptance testing? Acceptance testing is testing performed by the potential end-user or customers to check if the software conforms to the business requirements and can be accepted for use.

What is UAT Testing? Ans UAT testing is the last phase of the testing lifecycle. Its main focus is to validate that software is working in accordance with business requirements. It also ensures that the application is user-friendly and can handle complex scenarios at its best before releasing the product to real-world users.

What is End-To-End Testing? End-to-End testing is a type of testing where the entire application undergoes testing, to test each functionality of the software is working as expected and there is no loophole remaining in it. It ensures that the application is user-friendly and meets the business requirements. What is alpha testing?

Alpha testing is a type of acceptance testing that is performed testers or the internal employees of the organization at the developer site. What is beta testing? It allows users to provide direct input about the software to the development company. What is Adhoc Testing? Adhoc testing is an unstructured way of testing that is performed without any formal documentation or proper planning. What is monkey testing? Monkey testing is a type of testing that is performed randomly without any predefined test cases or test inputs.

What are the different sections present in SRS? User characteristics. Software requirements. Hardware requirements. Performance requirements. Use cases. Security and reliability requirements. How long do u spend on understanding SRS? It depends on the familiarity of the domain and complexity of the project. For a new complex domain, we manage around 15 pages per day. After understanding the SRS what do you do? My lead asks for presentation of the functionalities i am assigned with if i am in a position to explain the functionalities clearly to the team, then i am considered as comfortable with functionalities.

Should you understand the whole project functionality or only the functionality assigned to you? I should have a big picture of the whole project. In other words i should have an overview of the whole project and detailed screen and field level understanding of the assigned functionalities.

What are the different models generally followed in documenting requirements? Two models are followed in documenting the requirements which are usecase model and paragraph model.

Now a days almost all companies follow the usecase model where the requirements are written by stating thier clear objectives and explained with the help of screen shots. You can answer anything like approx pages. This question is asked just to cross check whether u have seen SRS or not. What will be the problem without SRS? Hence we will not able to test the project in depth and deliver the best quality product.

BRS is business requirement specification which is usually prepared before preparing an srs. This document gives a high-leval view of what is being required by the customer to meet business needs.

What is technical requirements specification? This is also called as high-leval design, which consists of different modules present in the project. Review is a meeting in which a work product is verified by set if members stake holders. Explain the review process you follow in your organization? The various phases of the review process followed in my organization are:. Planning :. Kick - off :. Individual preparation :. Review Meeting :.

Rework :. Follow - up :. What are the roles present in the review? The author is the person who has created the item to be reviewed. Reviewer :. The reviewer are the attendees of the review who attempt to find errors in the item under review.

The scribe or recorder is the person who is responsible for documenting issues raised during the process of the review meeting. Is a review of a software work product by colleagues?

What is the difference between static and dynamic testing? Static testing means testing the project without executing the software and dynamic testing means testing the project by executing the software.

To conduct dynamic testing you must use application screens and enter valid and invalid inputs and verify the application behavior. For static testing, we do not use any screens of application instead we use static techniques like review.

During review, experts go through each line of the work products like requirement document, design document and identify mistakes in these documents. Any mistakes identified during this review are nothing but defects in the work product.

I want you to choose one among static and dynamic testing for your project. Which one will you choose and why? According to me both are equally important and both of them contribute equally for the project success. Answer: End TO End testing system is a way of testing an application to ensure whether or not it is acting as expected to be working. It aims at conducting a test at the flow of the application beginning from the start to the endpoint.

End To End testing system scrutinizes the complete flow of the system. The End to End testing confirms that the data integrity is maintained in between the different system components and the systems. Answer: As per Top-Down Approach the testing procedure is conducted from the top to bottom. At the first place, the high-level modules undergo the testing procedure followed by the low-level modules and then at the end the integration of the low-level modules to a high level is done to make sure that the system is working as required.

As per the Bottom-Up Approach the testing procedure is carried out from the bottom to the top. At the first place, the low-level modules undergo the testing procedure which is then followed by the high-level modules and then at the end the integration of the high-level modules to a low level is done to make sure that the system is working as required. Answer: The main objective of conducting System testing is to make sure that the system works as per the specified requirements.

Whereas the major objective of the Integration testing is to test the interface in between the two different software units. It is a category of software testing where the individual units are collected together and tested as a whole. The main aim of this level of testing is to find out the faults in the interaction between integrated units.

Answer: The Big Bang Approach is a method of integration testing strategy which necessitates side by side checking of all the system components. Its main advantage is that the tester can check the work of the entire system and its components. Answer: Sanity Testing is conducted throughout the release phase to determine for the main functionalities of the application without going into many details.

It is also known as a subdivision of Regression testing. It is a level of Software Testing which is conducted once the software build is received along with minor changes in code or functionality to have a concrete proof that the bugs have been corrected and no further problems come up as a reason of these changes. Its purport is to make be sure that the proposed functionality works roughly as it is required.

Answer: Alpha testing is done by the developers who develop the software and testers. Sometimes it can be observed that the alpha testing is conducted by the purchaser or outsourcing team with the existence of developers or testers. Beta testing is to be conducted by a specified number of ultimate users before delivery. Generally, it is conducted at the place of the end-user. Gamma testing is performed to check the specified needs when the software is ready to be released.

It is usually done at the place of the ultimate user. It is performed at the first hand by omitting all the in-house testing activities. You need to be confident while giving the interview. A simple no is better than giving some random non-answer and adding unnecessary details if you do not know the answer to any question asked.

Candidates that are straightforward and honest are preferred over those pretending to be know-it-alls! The interviewer is more interested in knowing you as a technical person.

So, all the very best! Do let us know the Manual Testing Interview questions you faced in the interview that are not covered here so that we can add those here for the benefit of the Testing community. The questions are most frequently asked in manual testing interview. Share with your friends or anyone who is preparing for an interview to be a software tester. Simran works at Hackr as a technical writer. She enjoys writing about any tech topic, including programming, algorithms, cloud, data science, and AI.

Traveling, sketching, and gardening are the hobbies that interest her. View all posts by the Author. Superb post!!! Don't have an account? Sign Up. Already have an account? Software Testing and Interview Questions. Software Testing Tutorials. Related Tutorials Data Science. Intro to Programming. Recommended Learning Manual Testing abodeqa. Testing JavaScript Applications frontendmasters. View More. Simran Kaur Arora.

Table of Contents. Question: Define Static Testing? Question: Explain the various types of manual testing? Question: What is API testing? Question: Explain the difference between system testing and integration testing? Question: What is test closure? Question: Explain the pesticide paradox? How to overcome it? Question: Explain the difference between smoke testing and sanity testing? Question: How will you determine when to stop testing? We can run around test cases per day.

Note: For these types of questions , always remember the ratio: x test cases we can write, 3x test cases we can review, and 5x test cases we can execute per day. The testing team is not good Developers are super Product is old All of the above The correct answer is testing team is not good because sometimes the fundamentals of software testing define that no product has zero bugs.

We can track the bug manually as: Identify the bug. Make sure that it is not duplicate that is, check it in bug repository. Prepare a bug report. Store it in bug repository. Send it to the development team. Manage the bug life cycle i. Tracking the bug with the help of automation i. The software can have a bug for the following reasons: Software complexity Programming errors If no communications are happening between the customer and the company, i. Modification in requirements Time pressure.

We can stop testing whenever we have the following: Once the functionality of the application is stable. When the time is less, then we test the necessary features, and we stop it. The client's budget.

When the essential feature itself is not working correctly. We can write test cases for the following types of testing: Different types of testing Test cases Smoke testing In this, we will write only standard features; thus, we can pull out some test cases that have all the necessary functions.

Therefore, we do not have to write a test case for smoke testing. Integration testing Yes, we write the test case for integration testing. System testing Yes, we write the test case for system testing. Acceptance testing Yes, but here the customer may write the test case.

Compatibility testing In this, we don't have to write the test case because the same test cases as above are used for testing on different platforms. Adhoc testing We don't write the test case for the Adhoc testing because there are some random scenarios or the ideas, which we used at the time of Adhoc time. Though, if we identify the critical bug, then we convert that scenario into a test case.

Performance testing We might not write the test cases because we will perform this testing with the help of performance tools.

Usability testing In this, we use the regular checklist; therefore, we don't write the test case because here we are only testing the look and feel of the application. Accessibility testing In accessibility testing, we also use the checklist. Reliability testing Here, we don't write the manual test cases as we are using the automation tool to perform reliability testing.

Regression testing Yes, we write the test cases for functional, integration, and system testing. Recovery testing Yes, we write the test cases for recovery testing, and also check how the product recovers from the crash. Security testing Yes, we write the test case for security testing.

Globalization testing: Localization testing Internationalization testing Yes, we write the test case for L10N testing. Yes, we write the test case for I18N testing.

Traceability matrix Test case review In this, we will make sure that each requirement has got at least one test case. In this, we will check whether all the scenarios are covered for the particular requirements. Following are the significant differences between the use case and the test case: Test case Use Case It is a document describing the input, action, and expected response to control whether the application is working fine based on the customer requirements.

It is a detailed description of Customer Requirements. It is derived from test scenarios, Use cases, and the SRS. While developing test cases, we can also identify loopholes in the specifications.

A business analyst or QA Lead prepares it. First, we will see how we perform manual testing: Different types of testing Scenario Smoke testing Checks that basic functionality is written or not.

Integration testing Combine pen and cap and integrate other different sizes and see whether they work fine. Compatibility testing Various surfaces, multiple environments, weather conditions, and keep it in oven and then write, keep it in the freezer and write, try and write on water. Adhoc testing Throw the pen down and start writing, keep it vertically up and write, write on the wall.

Performance testing Test the writing speed of the pen. Usability testing Check whether the pen is user friendly or not, whether we can write it for more extended periods smoothly.

Accessibility testing Handicapped people use them. Reliability testing Drop it down and write, and continuously write and see whether it leaks or not Recovery testing Throw it down and write. Globalization testing Localization testing Price should be standard, expiry date format. Internationalize testing Check whether the print on the pen is as per the country language.

Now, we will see how we perform automation testing on a pen: For this take a roller, now put some sheets of paper on the roller, then connects the pen to the motor and switch on the motor. Reinforcement Learning. R Programming. React Native. Python Design Patterns. Python Pillow. Python Turtle. Verbal Ability. Interview Questions. Company Questions.

Artificial Intelligence. Cloud Computing. Data Science. Angular 7. Machine Learning. Data Structures. Operating System. Computer Network. Compiler Design. Computer Organization. Discrete Mathematics. Ethical Hacking. Computer Graphics. Software Engineering. Web Technology.

Cyber Security. C Programming. Control System. Data Mining. Data Warehouse. Javatpoint Services JavaTpoint offers too many high quality services. Regression is a type of software testing that checks the code change does not affect the current features and functions of an application. Functional testing is a testing technique which checks that function of the application works under the requirement specification.