Testing

Question 1

Which software is used for manual testing?

Answer 1

1. Browser DevTools
2. React Developer Tools
3. JIRA + Zephyr/TestRail

Question 2

What is unit testing, and why is it important?

Answer 2

Unit testing is the practice of testing individual pieces of code—usually functions or components—in isolation to verify that they work correctly.

1. Catches Bugs Early: Detects issues at the source before they escalate into bigger problems.
2. Improves Code Quality: Forces developers to write modular, testable, and cleaner code.
3. Simplifies Refactoring: Makes it safer and easier to change or improve code without breaking functionality.
4. Documents Code Behavior: Tests serve as executable documentation showing how units are supposed to work.
5. Speeds Up Debugging: When a test fails, it immediately points to the problematic part of the code.
6. Supports Continuous Integration: Automated unit tests help maintain stability by catching regressions during builds.

Question 3

What is the primary purpose of integration testing?

Answer 3

The primary purpose of integration testing is to verify that different individual modules or components of a software system work correctly together when combined.

Question 4

What is E2E testing, and why do we need it?

Answer 4

End-to-End (E2E) testing is a type of software testing that validates the entire application flow — from the user interface down to the backend and databases — to ensure the whole system works as expected in a real-world scenario.

1. Validate User Experience: Ensures users can complete tasks successfully, as intended.
2. Catch Integration Issues: Detects problems that unit or integration tests might miss, especially when multiple subsystems interact.
3. Verify Real Environment Behavior: Tests the app in conditions close to production, including network, browser quirks, and backend responses.
4. Reduce Risk of Regression: Automated E2E tests catch bugs introduced by code changes that affect overall workflows.
5. Build Confidence Before Releases: Helps stakeholders trust that critical features are functioning properly.

Question 5

What is the difference between debugging in the browser and in IDE?

Answer 5

Browser debugging:
1. Runs in the browser runtime, as opposed to within development environment
2. Has a scope of client-side code only, as opposed to client-side and server-side code
3. Uses the DevTools, as opposed to the debugger built into IDE
4. Features DOM/CSS inspection, network logs; as opposed to Rich code introspection, test debugging
5. Is best for quick fixes, UI & network issues, as opposed to deep debugging, backend and tests