Software Testing is the process of reviewing a system or its component(s) to find if it completes the specified requirements or not. Testing is the method of capital punishment a system so as to search out any gaps, errors, or missing necessities in terms of the particular necessities. In testing, a check state of affairs is what to be tested and an action at law is a way to be tested. In alternative words, a check state of affairs may be a cluster of check cases.
Below are some important FAQs which help every interviewer.
1. WHAT IS SOFTWARE TESTING?
Software testing is a validation process in which the tester has to make sure if a system works as per the business requirements. It qualifies a system on various aspects such as functionality, validation, usability, performance, load, User interface, etc.
2. WHAT IS STATIC TESTING? WHEN DOES IT START AND WHAT DOES IT COVER?
Static testing is a testing technique where testing is being performed without executing the code. It is usually performed early during the software development life cycle. The main purpose of performing static testing is to avoid code level mistakes. Static testing is more cost-effective than dynamic testing.
3. IS IT POSSIBLE TO ACHIEVE 100% TESTING COVERAGE? HOW WOULD YOU ENSURE IT?
Testing is a never-ending process so we cannot perform 100% testing but we can use various strategies to achieve effective testing. Tester has to make sure if all the functionalities should work with positive and negative data. In order to test, tester has to prepare set of test data with the equivalence partioning, boundary value analysis and error guessing technique. The tester should also check the performance of the functional flow. Usability, UI, configuration and compatibility testing also needs to be performed during testing. Important thing is that tester should get the confidence that system is fully operational and can deploy it to production.
4. WHAT ARE UNIT TESTING AND INTEGRATION TESTING?
Unit and Integration testing are performed by developers because they have to check the source code of the units. Unit testing has many names such as module testing or component testing. Many times, it is the developers who test individual units or modules to check if they are working correctly. Whereas, integration testing validates how well two or more units of software interact with each other. There are three ways to validate integration: Big Bang approach Top-down approach Bottom-up approach.
5. CAN WE DO SYSTEM TESTING AT ANY STAGE?
No. System testing should start only if all modules are in place and they work correctly. Once functionality testing is done then the tester should go with system testing. However, it should be performed before UAT (user acceptance testing).
6. DIFFERENCE BETWEEN BUG, DEFECT AND ERROR.
DEFECT: It can be simply defined as a variance between expected and actual. The defect is an error found AFTER the application goes into production. In other words Defect is the difference between expected and actual result in the context of testing. It is the deviation of the customer requirement.
ERROR: An error is a mistake, misconception, or misunderstanding on the part of a software developer. A mistake in code is called error. Error is usually found by developer. Error includes syntax error or wrong variable and data type definition, invalid arguments, wrong loop etc…
BUG: A bug is the result of a coding error. During testing when tester finds some variation in actual and expected results then tester reports that defect/issue to the development team. The development team verifies the defect and they accept it then it is called as bug. Bug is a terminology of Tester.
FAILURE: A failure is the inability of a software system or component to perform its required functions within specified requirements. When product goes live and it is not working as an expected and then problem is reported by many end to end customers then it is called as Failure.
7. WHAT IS SEVERITY AND PRIORITY?
Severity: Severity means how severe a defect is affecting the functionality. It is related to quality standards and that is why it is defined by Tester.
Priority: Priority means how fast a defect has to be fixed. Priority decides the order in which defects should be fixed.
Read More: Software Testing Interview Questions Answers
Unicode Technologies 