Software Testing Fundamentals:
✅ 1. What is software their types?
Answer:
Software is a collection of instructions, programs, or data that tells a computer how to work. It allows users to interact with hardware and perform specific tasks.
There are Three types of software:
1) System software (like Windows, Linux)
2) Application software (like MS Word, WhatsApp).
3) Programming software (like Compiler, debugger and interpreter)
Example:
Google Chrome is a software used for browsing the internet.
Windows is a system software that manages the computer’s hardware and allows other applications to run.
Eclipse is a programming software used to write, compile, and run Java applications.
✅ 2. What is testing?
Answer:
Testing- it is process of finding deviation b/w expected and actual result.
It ensures the quality, performance, and reliability of the application. The purpose of testing is to find bugs, verify that the software meets the requirements, and deliver a bug-free product to users.
Example:
If a login page accepts the wrong password and still logs in, it means testing is needed to catch and fix this bug.
✅ 3. What are the types of layers in software?
Answer:
Most modern software applications follow a 3-layer architecture:
-
Presentation Layer (UI) – Front-end visible to users (buttons, forms).
-
Business Logic Layer – Handles rules, logic, and processing.
-
Data Layer (Database) – Stores and retrieves data from the database.
Example:
In an e-commerce site:
-
UI shows product listings (Presentation),
-
Adding to cart applies discounts (Business Logic),
-
Order info is stored in a database (Data Layer).
✅ 4. What are the types of application software?
Answer: There are several types of application software, each designed to perform specific tasks. Below are the main types with examples:
-
General-Purpose Application Software –
These are commonly used by all users for general tasks like writing, calculating, or browsing.
Example: MS Word, Excel, Chrome -
Specific-Purpose Application Software –
This type is designed to perform a specific task or serve a particular domain.
Example: Billing software, Payroll systems, Hospital Management System -
Customized Application Software –
It is tailor-made for a specific user or organization according to their requirements.
Example: Custom CRM for a company -
Open-Source Application Software –
These are free to use and the source code is available for modification.
Example: GIMP, LibreOffice -
Freeware –
It is free to use but the source code is not available for editing.
Example: Skype, Adobe Acrobat Reader -
Shareware –
It is distributed for free initially but requires payment after a trial period.
Example: WinRAR, trial version of antivirus
✅ 5. How will you know the requirements of the application?
Answer:
To understand the application requirements, I follow these steps:
-
Read the SRS or BRD documents shared by the Business Analyst or client.
-
Attend requirement meetings or walkthrough sessions to understand the business needs.
-
Go through user stories if it’s an Agile project.
-
Ask questions whenever something is unclear — I prefer to clarify early.
-
Check prototypes or wireframes if available, to understand the UI and flow.
-
Explore the application (if accessible) to get a better idea of its behavior.
In short: I use documents, meetings, and discussions to understand the requirements clearly before starting testing.
✅6. How many ways can we do software testing?
Answer:
Software testing can be done mainly in two ways:
-
Manual Testing –
In this method, the tester tests the application manually, without using any tools or scripts.
It involves checking the functionality, UI, and user flow by hand.
Example: Clicking buttons, filling forms, checking results on the screen. -
Automation Testing –
In this method, the tester writes scripts using tools to automatically test the application.
It saves time, especially for repeated tests like regression testing.
Example: Using Selenium to run login tests automatically.
Manual Testing should be performed when:
-
The project is small or short-term – Manual testing is quicker to start.
-
Requirements keep changing – Automation is not useful if scripts need frequent updates.
-
Exploratory, UI, or usability testing is needed – Human observation is best here.
-
Testing once or twice only – Not worth spending time on automation.
-
Early stages of development – When features are still being built or unstable.
Automation Testing should be performed when:
-
The test cases are repetitive – Like regression tests after every build.
-
The project is large and long-term – Saves time and effort in the long run.
-
Tests need to be run on multiple browsers or devices – Automation can handle parallel execution.
-
Performance, load, or stress testing is needed – Tools can simulate thousands of users.
-
The application is stable – Ideal time to invest in writing automation scripts.
One-line summary (for quick interview use):
Manual testing is best for new, changing, or user-focused areas; automation is best for stable, repetitive, or large-scale testing.
✅09. What are the challenges or limitations of Manual Testing?
Answer:
Manual testing is useful but has several challenges and limitations:
-
Time-Consuming:
Testing each feature manually takes a lot of time, especially for large projects. -
Repetitive Work:
Running the same test cases again and again (like in regression) can become boring and lead to missed bugs. -
Human Errors:
Since testers do it manually, there’s a higher chance of mistakes or skipping steps. -
Not Suitable for Performance Testing:
Manual testing cannot simulate thousands of users or load — tools are needed for that. -
Limited Coverage:
Due to time constraints, testers may not cover every possible test scenario manually. -
Slower Feedback:
Manual testing gives slower feedback after code changes, which delays releases. -
Not Scalable:
As the project grows, manual testing becomes harder to manage and track. -
High Cost in Long Term:
While cheap at the start, manual testing becomes expensive due to the effort and time needed in every cycle.