One of the best software Training & Placement center in Nagercoil. In our Sector we are providing specialized training for Engineering & diploma students

1. Software Testing

2. What is meant by software testing?
Software testing is the process of evaluation a software item to detect differences between
given input and expected output.
Software testing is a process that should be done during the development process.
Software testing is a Verification and Validation process.

3. Manual Testing
Manual testing is a process of executing the test cases manually.
Manual Testing concepts does not require knowledge of any testing tool.
Manual testing is to ensure that the application is error free.

4. Automation Testing
Automation testing is the process of executing test script using automated tools.
The test automation engineer will write the test script or use the automation testing tools to
execute the application.
The automation testing process is a time-saving process.

5. Software Development Life Cycle [SDLC]
Software development life cycle is essentially a series of steps, or phases, that provide
a model for a development and lifecycle management of an application.
1. Requirement analysis.
Requirements analysis or requirements engineering is a process used to
determine the needs and expectations of a new product.

6. 2. Design.
The software design phase is the first step in SDLC (Software Design Life Cycle),
which transform user requirements into some suitable form. SDLC requires a
designing step that models how the application will work
3. Developing
This is the phase where the program itself is written out, either using a single
developer or a large team each working on different parts of the development.

7. 4. Testing
Applications must be tested continuously to ensure that they are going to run well
together. This reduces the number of bugs that users can encounter when using the
application.
5. Implementation
An application is deployed once testing is completed, which makes it available
to users.

8. 6. Maintenance
Once the application has been deployed and is being used, the final phase discovers
bugs that slipped through the cracks during testing and resolves them

9. Software Testing Life Cycle [STLC]
STLC is a Testing Process which has specific steps to be executed in a definite sequence
to ensure that the quality goals have been met. Each phase has different goals and
deliverables.
1. Test Plan
During this phase, the test strategy is outlined.
This strategy includes tools needed, testing steps, and roles and responsibilities.

10. 2. Test Case Design.
During this phase, test cases are created. Each case defines test inputs, procedures,
execution conditions, and anticipated results.
3. Test Case Execution.
During this phase, features are tested in the deployed environment, , using the established
test cases.
Expected test results are compared to actual and results are gathered to report back to
development teams.

11. 4. Test Log
Provides an Integrated management environment in which you will create and manage, not
just your test cases, but your entire test plan.
TestLog inline reports quickly generate statistics, which show the progress of your project
and estimate if the project is still keeping to the schedule.

12. 5. Defect Tracking
Defect tracking process is used by the quality assurance personnel to report, track and
manage the issues found in the software.
Defect tracking tools provide several features that helps to effectively manage the
bugs in a hassle free manner.

13. 6. Reporting Defects.
A defect report is more than just a description of the defect.
Defect report is often divided into several 'fields', in which the various details can be
laid down that are necessary for the management of the defect and for obtaining
meaningful information from the administration.

14. Bug Life Cycle
New
Assigned
Resolved
Reopened
Verified
Close

15. Verification
Verification is the process to make sure the product satisfies the conditions imposed at the start
of the development phase. In other words, to make sure the product behaves the way we want it
to.
Ex: document reviews, inspect, product walkthroughs, and desk-checking. [ does not
require executing code]
Validation
Validation is the process to make sure the product satisfies the specified requirements at the end
of the development phase, In other words, to make sure the product is built as per customer
requirements.
Ex: Verifying the expected output 5*5 should be 25 [ checking the output by executing the
code]

16. Basics of software testing.
Blackbox Testing
Blackbox testing is a testing technique that ignores the internal mechanism of the
system and focuses on the output generated against any input and execution of
the system. It is also called as Functional Testing.

17. Whitebox Testing
Whitebox testing is a testing technique that takes into account the internal
mechanism of a system. It is also called as structural testing and glass box
testing.
Black box testing is used for validation and white box testing is used for
verification.

18. Types of Testing
There are many types of testing like
Unit Testing
Integration Testing
Functional Testing
System Testing
Stress Testing
Performance Testing
Usability Testing

19. Acceptance Testing
Regression Testing
Beta Testing
Unit Testing
Unit Testing is the testing of an individual unit or group of related units. It falls under the
class of white box testing. It is done by the programmer to test that the unit he/she has
implemented id producing expected output against given output

20. Integration Testing
Integration testing is a testing in which a group of components are combined to produce
output. Also, the interaction between software and hardware is tested in integration testing
if software and hardware components have any relation. It may fall under both white box
and black box testing.
Functional Testing
Functional testing is the testing to ensure that the specified functionality required in the
system requirements works. It falls under the class of black box testing.

21. System Testing
System testing is the testing to ensure that by putting the software in different
environments (e.g. Operating Systems) it still works. System testing is done with full
system implementation and environment. It falls under the class of black box testing.
Stress Testing
Stress Testing is the testing to access the speed and effectiveness of the system and to
make sure it is generating results within a specified time as in performance requirements.
It falls under the class of black box testing.

22. Performance Testing
Performance testing is the testing to access the speed and effectiveness of the system and
to make sure it is generating results within a specified time as performance requirements.
It falls under the class of black box testing.
Usability Testing
Usability testing is performed to the perspective of the client, to evaluate how the GUI is
User friendly? How easily can the client learn? After Learning how to use, how
proficiently can the client perform? How pleasing is it use its design? This falls under the
class if black box testing.

23. Acceptance testing
Acceptance testing is often done by the customer to ensure that the delivered product
meets the requirements and works as the customer expected. It falls under the class of
black box testing.
Regression Testing
Regression testing is the testing after modification of a system, component, or a group of
related units to ensure that the modification is working correctly and not damaging or
imposing other modules to produce unexpected results.

24. Beta Testing
Beta testing is the testing which is done by the end users, a team outside development, or
publicly releasing full pre- version of the product which is known as Beta version. The aim
of Beta version is to avoid unexpected errors. It falls under class of Black box testing.

25. What is Test Case?
A Test Case is a set of preconditions steps to be followed with input data and expected
behaviour to validate the functionality of a system.

26. What is Business validation Test case?
A Test case is prepared to check business condition or business requirements is called business
validation test case.
For e.g:
● Scenario: Verify that Application automatically connects to the Servers, if user creates new
profile.
○ Test Case 1: Create a new profile and verify that it created successfully.
○ Test Case 2: Verify that Application succeeded on connect to the Servers.

27. What is a Good Test Case?
A Test case that have high priority of catching defects.
Priority #1) Immediate/Critical (P1)
This has to be fixed immediately within 24 hours. This generally occurs in cases when an
entire functionality is blocked and no testing can proceed as a result of this.

28. Priority #2) High (P2)
These defects should be resolved once the Critical issues are solved.
Priority #3) Medium (P3)
Once the Critical and the High priority bugs are done, we can go for the medium priority
bugs. All the Minor severity defects fall into this category

29. Priority #4) Low (P4)
This defect can be resolved in the future and does not need any immediate attention and
the Low severity defects fall into this category

30. What is use case testing?
Validating a software to confirm whether it is developed as per the use cases or not is
called use case testing.
Ex : Consider a scenario where a user is buying an Item from an Online Shopping Site. The user will First log in to
the system and start performing a Search. The user will select one or more items shown in the search results and he
will add them to the cart.
After all this, he will check out. So this is an example of logically connected series of steps which the user will
perform in a system to accomplish the task.

31. What is showstopper Defect?
A defect which is not permitting to continue further testing is called showstopper Defect.
A showstopper defect is a defect that stops from continuing test scripts and doesn't let you
proceed to the next level.

32. Smoke Testing
It is a kind of Quick Test Carried out on the application to determine whether the
application is testable or not.
We perform smoke testing on a new build. The smoke tests qualify the build for further
formal testing. The main aim of smoke testing is to detect early major issues.

33. Sanity Testing
Verifying the critical ( important) functionality of the software on new build to decide
whether to carry further testing or not.
It is a quick and basic test (or set of tests) to ensure that the code changes made are
working properly without any bugs. It is a subset of Regression testing and is usually
executed after the software product has passed the Smoke test.

34. Client/Server Testing
This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front - end backend.
The application launched on front end will be having forms and reports which will be
monitoring and manipulating data.
E.G Applications developed in VB, VC++, Core Java, C, C++, D2K, PowerBuilder etc.,
The backend for these applications would be MS Access, SQL Server, Oracle, Sybase,
Mysql, Quadbase.

35. The tests performed on these types of applications would be
-User interface testing
-Manual Support testing
-Functionality testing
-Compatibility testing
-Intersystem testing

36. Web Testing
This is done for 3 tier application (developed for internet/ Intranet/ xtranet) Here we will
be having Browser, web server and DB server.
The applications accessible in browser would be developed in HTML, DHTML, XML,
Javascript etc. (We can monitor through these applications)
Applications for the web server would be developed in Java, ASP, JSP, VBScript,
Javascript, Perl, Cold Fusion, PHP etc. (All the manipulations are done on the web server
with the help of these programs developed)

37. The DBserver would be having oracle, sql server, sybase, mysql etc. (All base is stored in
the database available on the DB server)
The tests performed on these types of applications would be
- User Interface testing
- Functionality testing
- Security testing
- Browser compatibility testing
- Load/ stress testing
- Interoperability testing/Intersystem testing
- Storage and data volume testing

38. What is Dynamic testing
It is the testing done by executing the code or program with various input values and
output is verified
Ex: login functionality of any application, like Google's gmail.com. Verifying login
functionality with different input values.

39. What is GUI Testing?
GUI or Graphical User Interface testing is the process of testing software user interface
against the provided requirements/mockups/HTML designs.
Ex: Check the size, location, breadth, length, and character or number acceptance of all the
buttons.

40. What is Formal Testing?
Software verification carried out by following test plan, test procedures and proper
documentation with an approval from customer.
Ex: Formal testing follows a systematic process called Software Testing Life Cycle
(STLC).There are multiple steps taken in formal testing:
● Requirement Analysis.
● Planning about tests.
● Documentation of Test Cases.
● Setting up the Test Environment.
● Execution of Tests.
● Closure of Tests.

41. What is Monkey Testing?
Testing conducted on an application without any plan and carried out with tests here there
to find any system crash with an intention of finding tricky defects is called monkey
defects.
Ex: Providing random inputs to the application without any test cases to crash the system.

42. What is non functional testing?
Validating various non functional aspects of the system such as user interfaces, user friendliness
security, compatibility, load, Stress and performance etc is called non functional testing.
Ex: Application load time should not be more than 5 secs up to 1000 users accessing it
simultaneously. - Performance Testing
Software should be installable on all versions of Windows and Mac - Compatibility
Testing

43. What is Risk Based Testing?
Identifying the critical functionality in the system then deciding the orders in which these
functionality to be tested and applying testing.
Ex: Testing the functionality which has the highest impact and probability of failure.

44. What is Early Testing?
Conducting testing as soon as possible in development life cycle to find defects at early
stages of SDLC.
Early Testing is helpful to reduce the cost fixing defects at later stages of STLC. Early
Testing saves time and money.

45. What is Exhaustive Testing?
Testing functionality with all valid, invalid inputs and preconditions is called exhaustive
testing.
Ex: Checking the password. Consider if application allows 12 possible inputs then the user
can enter the password of length 12 with 6 different combinations.

46. What is Defect clustering?
Any small module or functionality may contain more number of defects - Concentrate
more testing on these functionality.
What is Pesticide Paradox?
If prepared test case are not finding defects. add/revise test cases to find more defects.

47. What is static Testing?
Manual Verification of the code without executing the program is called as static testing.
In this Process issues are identified by using checking code, requirement and design
documents.
Ex: Some of the issues checked are:
● Logic errors
● Design flaws
● Dead code
● Unused or uninitialized variables
● Infinite loops

48. What is Positive Testing?
Testing Conducting on the application to determine if system works, Basically known as
“Test to Pass” approach.
Ex: Entering values up to 10 will be acceptable by the system and any other values apart
from this should not be acceptable. To do positive testing, set the valid input values from 0
to 10 and check whether the system is accepting the values.

49. What is Negative Testing?
Testing Software with negative approach to check if system is not “showing error when
not supposed to” and “not showing error when supposed to”.
Ex: Entering values up to 10 will be acceptable by the system and any other values apart
from this should not be acceptable. To do Negative testing, set the input values greater
than 10 and check whether the system throws error message or not.

50. What is End to End Testing?
Testing the overall functionality of the system including the data integration among all the
modules is called end to end testing.
Ex: Checking the application’s workflow from beginning to end in real user scenarios.

51. What is Exploratory Testing?
Exploring the application, understanding the functionality, adding (or) modifying existing
test cases for better testing is called exploratory testing.
Example: You might perform one test and then ask yourself, “What if I tried this? What if
I didn’t do that?”

52. What is Security Testing?
Validating whether all security conditions are properly implemented in the software (or)
not is called Security Testing.
Ex: Non registered users should not be allowed to access the application or system.

53. What is stress Testing?
Checking the application behaviour under stress conditions.
(OR)
Reducing the system resources and keeping the load as constant checking how does the
application is behaving is called stress testing
Ex: Consider education board result website. On the day of some results, many students,
users, and applicants will logins to the particular to check their grades.

54. What is Performance Testing?
Process of measuring various efficiency characteristics of a system such as response time,
through put, load stress transactions per minutes transaction mix.
Ex:
Speed – Determines whether the application responds quickly
Scalability – Determines the maximum user load the software application can handle.
Stability – Determines if the application is stable under varying loads

55. What is Load Testing?
Analyzing functional and performance behaviour of the application under various
condition is called Load Testing.
Ex: Verifying how the software application behaves while being accessed by multiple
users simultaneously.

56. What is Process?
A Process is set of practices performed to achieve a give purpose, it may include tools,
methods, materials and or people.
What is Software Configuration Management?
The Process of identifying, Organizing and controlling changes to software development
and maintenance.
(or)
A methodology to control and manage a software development project.

57. What is Test Scenario?
Identify all the possible areas to be tested (or) what to be tested.
What is Severity?
It defines the important of defect with respect to functional point of view i.e. how
critical is defect with respective to the application.

58. What is Priority?
It indicates the importance or urgency of fixing a defect.
Priority of the defects can be classified as : Immediate/Critical/High/Medium/Low

59. What is Re- Testing?
Re - Testing the application to verify whether defects have been fixed or not.
Example: Say, Build 1.0 was released. While testing the Build 1.0, Test team found some
defects (example, Defect Id 1.0.1 and Defect Id 1.0.2) and posted. The test team tests the
defects 1.0.1 and 1.0.2 in the Build 1.1 (only if these two defects are mentioned in the
Release Note of the Build 1.1) to make sure whether the defects are fixed or not.

60. What is Regression Testing?
Verifying existing functional and non functional area after making changes to the part of
the software or addition of new features.
Tests to cover a cross-check for every part of the code tampered with.
Tests for areas most likely affected due to these changes.

61. What is Recovery Testing?
Checking if the system is able to handle some unexpected unpredictable situations is called
recovery testing.
Ex: During multiple sessions on your computer, suddenly remove the power supply of the
system. If after restarting all the applications and web pages get reloaded then the system
is damage-proof.

62. What is Compatibility Testing?
Checking if the application is compatible to different software and hardware is called
compatibility testing
Example : Application that we can access through both mobile and PC

63. What is Test Strategy?
It is a part of test plan describing how testing is carried out for the project and what testing
types needs to be performed on the application.
What is entry criteria and exit criteria software testing?
The Entry criteria is the process that must be present when a system begins, like,

64. ● SRS - Software
● FRS
● Use Case
● Test Case
● Test Plan
The Exit Criteria ensures whether testing is completed and the application is ready for
release like,
● Test Summary Report,
● Metrics,
● Defect Analysis Report,

65. What is Gamma Testing?
Gamma Testing is done when the software is ready for release with specified
requirements, this testing is done directly by skipping all in-house testing activities.
Only a limited number of users perform gamma testing, and testers do not participate. The
checking includes the verification of certain specifications, not the whole product.
Feedback received after gamma testing is considered as updates for upcoming software
versions. But, because of a limited development cycle, gamma testing is usually skipped

66. What is Scalability Testing?
It is used to check whether the functionality and performance of a system, whether system
is capable to meet the volume and size changes as per the requirements scalability testing
is done using load test by changing various software, hardware configurations and testing
environments.

67. What is Data Driven Testing?
It is Automation testing process in which application is tested with multiple set of data with different
preconditions as an input to the script.
Some of them are as follows:
● Script arrays.
● Comma-separated values (CSV) files.
● Excel sheets.
● Database tables.
● Table variables.