The success of any software product in today's competitive environment depends on testing.
If you are preparing for a Junior level manual testing interview then please keep on reading. We have prepared a collection of questions to be asked in the interview which can help you with the preparation.
1. Define Errors: Any incorrect human action that produces a problem in the system.
2. Define Defect: Deviation between expected behaviour to the actual behaviour of the system.
3. Define Failure: Deviation identified by the end-user while using a system.
4. Why does software have defects?
5. Testing
It is a process of verifying whether we are developing the right product or not and also validating if the developed product is right or not.
6. Stating testing /verification
It's a process of verifying whether are we developing the right product or not
7. Validation /dynamic testing
It's a process of validating whether the developed product is right or not.
8. Software testing techniques
9. Levels of testing
-
Unit /Component testing
-
Integration testing
-
System testing
-
Acceptance testing
10. White box test
Testing is conducted on the source code by the developer to check if the source code is working as expected or not.
11. Black box testing
white box testing is generally done by the developer, whereas black box testing is done by test engineers.
12. Smoke testing
It is a kind of quick test carried out on the application to determine whether the application is testable or not.
13. Adhoc testing
If you test software without following any procedure and documentation it's called Adhoc testing,it's also called informal testing
14. Regression testing
It is a process of identifying the various feature in the modified build where there is a chance of getting affected and retesting these features
15. Exploratory testing
Understanding the system, modifying the test cases and executing those changes.
16. Non -Functional testing
Validating the various non-functional aspects of the system such as interfaces, user friendly, security, load, stress, compatibility and performance etc.
17. Globalisation testing
Checking if the application has a provision for setting and changing languages date and time format, currency format etc. It is designed for a global user.
18. Software testing life cycle (STLC) /Manual testing procedure.
19. Test plan: It is a day-to-day work plan that explains the scope, approach resources and work schedule etc. The test plan can be prepared by the test lead.
20. Test design techniques
Equivalence class partition (ECP)
Boundary value analysis (BVA)
decision table.
state transition testing
Use Case testing
21. Requirement traceability matrix (RTM)
Mapping between test cases and requirements is called a traceability matrix.
22. High servility
Runtime error, show stopper, Once the function is not working
23. Low severity
Bugs, Font, colours, Cosmetic etc.
24. Defect Age
The time interval between the date of detection and the date of closure is called defect age.
25. SDLC divided into two models
-
Sequential ->Waterfall model ,V model
-
teration -> RAD (Rapid Application development),Prototype, Spiral module.
26. Sequential models
These modules are best suited for small applications where all development activities are carried out in sequential order for the entire project.
27. Interactive models
These models are best suitable for big projects, in which a big project will be divided into modules then the application will be implemented module by module.
28. Waterfall model
It is a beginning approach to a development module where all development activities are carried out one after the other for the entire project.
29. Agile Model
-
Agile Model project is divided into various sprints
-
Each sprint contains high priority requirements
-
The time period of the sprint is typically 2 to 3 weeks
-
Daily screening meetings with the team share the status and potential issues.
-
Each sprint is released to the customer
-
User for critical applications
30. Q & A testing
Once system Level testing is approved, release the application for user acceptance testing (UAT), Once installed by the customer feedback is obtained for future enhancement and finding defects.
31. Stress testing
checking the application behaviour under stress conditions, In other words, reducing the system resources and keeping the load constant checking how the application behaves
32. Priority
Defines the importance of defects with respect to the client's point of view, which means how soon they should be fixed.
-
p1 Urgent
-
p2 high
-
p3 Medium
-
p4 Low
.
33. Severity
-
Critical
-
Major
-
Moderate
-
Minimum
34. What is the test case?
A test case is a document that has a set of conditions or actions that are performed on the software application in order to verify the expected functionality of the feature.
35. What’s the difference between verification and validation in testing?
|
Verification
|
Validation
|
|
It is a static analysis technique. Here, testing is done without executing the code. Examples include – Reviews, Inspection, and walkthroughs.
|
It is a dynamic analysis technique where testing is done by executing the code. Examples include functional and non-functional testing techniques.
|
36. 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 behaviour of an API.
37. What are the advantages of manual testing?
Merits of manual testing are:
-
It is a cheaper way of testing when compared to automated testing
-
Analysis of the product from the point of view of the end-user is possible only with manual testing
-
GUI testing can be done more accurately with the help of manual testing as visual accessibility and preferences are difficult to automate
-
East to learn for new people who have just entered into testing
-
It is highly suitable for short-term projects when test scripts are not going to be repeated and reused for thousands of times
-
Best suited when the project is at the early stages of its development
-
Highly reliable, since automated tests can contain errors and missed bugs
38. What are the drawbacks of manual testing?
De-merits of manual testing are:
-
Highly susceptible to human error and are risky
-
Test types like load testing and performance testing are not possible manually
-
Regression tests are really time-consuming if they are done manually
-
The scope of manual testing is very limited when compared to automation testing
-
Not suitable in very large organizations and time-bounded projects
-
The cost adds up, so, it’s more expensive to test manually in the long run
39. When should you stop the testing process?
-
The testing activity ends when the testing team completes the following milestones.
-
Test case execution
-
The successful completion of a full test cycle after the final bug fix marks the end of the testing phase.
-
Testing deadline
-
The end date of the validation stage also declares the closure of the validation if no critical or high-priority defects remain in the system.
-
Code Coverage(CC) ratio
-
It is the amount of code concealed via automated tests. If the team achieves the intended level of code coverage (CC) ratio, then it can choose to end the validation.
-
Mean Time Between Failure (MTBF) rate
-
Mean time between failure (MTBF) refers to the average amount of time that a device or product functions before failing. This unit of measurement includes only operational time between failures and does not include repair times, assuming the item is repaired and begins functioning again. MTBF figures are often used to project how likely a single unit is to fail within a certain period of time
40. Mention the different types of software testing.
Various types of Software Testing used by manual testers are as follows:
41. What is the purpose of end-to-end testing?
End-to-end testing is a testing strategy to execute tests that cover every possible flow of an application from its start to finish. The objective of performing end-to-end tests is to discover software dependencies and to assert that the correct input is getting passed between various software modules and sub-systems.
42. What kind of skills are needed for someone to become a software tester?
Software testers need skills such as:
-
Problem-solving skills
-
Excellent written and verbal communication skills
-
Detail-oriented
-
Able to handle the pressure
-
Can work solo or as a team member equally well
-
Organizational skills
-
Related technical skills
43. Explain the difference between alpha testing and beta testing.
Alpha testing is at the developer’s site before release. Potential clients conduct beta testing at their websites.
44. What’s a testbed?
It’s not furniture. A testbed is an environment used for testing an application, including the hardware as well as any software needed to run the program to be tested.
45. What’s GUI testing?
This tests the interface between the software and the end-user. Short for Graphics User Interface.
46. Define what is a critical bug.
A critical bug is a bug that has got the tendency to affect a majority of the functionality of the given application. It means a large piece of functionality or major system component is completely broken and there is no workaround to move further. The application cannot be distributed to the end client unless the critical bug is addressed.
47. Why is it impossible to test a program thoroughly or in other terms 100% bug-free?
It is impossible to build a software product which is 100% bug-free. You can just minimize the error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result.
Here are the two principal reasons that make it impossible to test a program entirely.
-
Software specifications can be subjective and can lead to different interpretations.
-
A software program might require too many inputs, too many outputs, and too many path combinations to test.
48. What is a top-down and bottom-up approach in testing?
Top-Down – Testing happens from top to bottom. That is, high-level modules are tested first and after that low-level modules. Lastly, the low-level modules are incorporated into a high-level state to guarantee the framework is working as it is expected to.
Bottom-Up – Testing happens from base levels to high-up levels. The lowest level modules are tested first and afterwards high-level state modules. Lastly, the high-level state modules are coordinated to a low level to guarantee the framework is filling in as it has been proposed.
49. Is it true that we can do system testing at any stage?
In system testing, all the components of the software are tested as a whole in order to ensure that the overall product meets the requirements specified. So, no. The system testing must start only if all units are in place and are working properly. System testing usually happens before the UAT (User Acceptance Testing).
50. Is there any difference between retesting and regression testing?
Possible differences between retesting and regression testing are as follows:
-
We perform retesting to verify the defect fixes. But, the regression testing assures that the bug fix does not break other parts of the application.
-
Regression test cases verify the functionality of some or all modules.
-
Regression testing ensures the re-execution of passed test cases. Whereas, retesting involves the execution of test cases that are in a failed state.
-
Retesting has a higher priority over regression. But in some cases, both get executed in parallel.
51. Differentiate between Positive and Negative Testing
|
Positive Testing
|
Negative Testing
|
|
Positive testing ensures that your software performs as expected. The test fails if an error occurs during positive testing.
|
Negative testing guarantees that your app can gracefully deal with unexpected user behaviour or incorrect input.
|
|
In this testing, the tester always looks for a single set of valid data.
|
Testers use as much nega ingenuity as possible when validating the app against erroneous data.
|
Please note that these top 51 questions are only meant to be used as guidance. We recommend that along with being thorough with the subject, in theory, you are also aware of the latest developments and key trends in the area.
