01 • Foundation
What is manual testing?
Manual testing is the process of evaluating software by performing test activities without using automated scripts to execute the tests.
A manual tester interacts with the application, compares actual behavior with expected behavior, investigates risks, and communicates findings to the development team.
Professional manual testing requires planning, observation, critical thinking, documentation, product knowledge, and clear communication.
What does a manual tester do?
- Reviews requirements and acceptance criteria
- Identifies test scenarios and risks
- Writes and executes test cases
- Performs exploratory testing
- Documents and reports defects
- Performs regression testing
- Communicates release-quality information
02 • Test Design
Test scenarios and test cases
Test scenario
A test scenario describes a high-level area or behavior that should be tested.
Verify that a registered user can log in to the application.
Test case
A test case provides the detailed steps, test data, conditions, and expected result needed to verify behavior.
A unique identifier used to track the test case.
Conditions that must exist before testing begins.
The actions the tester performs.
The accounts, values, or information used during testing.
The behavior the application should produce.
The behavior observed during execution.
03 • Test Coverage
Positive and negative testing
Positive testing
Positive testing verifies that the application works when users provide valid information and follow the expected path.
Enter a registered email address and the correct password. Verify that the user successfully reaches the account page.
Negative testing
Negative testing verifies that the application handles invalid information, unexpected actions, and error conditions correctly.
- Enter an incorrect password
- Submit an empty email address
- Enter an invalid email format
- Attempt to log in with an unknown account
- Click the login button repeatedly
04 • Boundary Testing
Test the edges
Boundary-value testing focuses on values at, directly below, and directly above an allowed limit. Defects frequently occur around these boundaries.
If a password must contain between 8 and 20 characters, test 7, 8, 9, 19, 20, and 21 characters.
05 • Testing Types
Exploratory and regression testing
Exploratory testing
Exploratory testing combines learning, test design, and test execution. The tester investigates the application while adapting tests based on observations.
- Begin with a testing goal or charter
- Explore realistic customer behavior
- Observe unexpected results and risks
- Take notes and document discoveries
Regression testing
Regression testing verifies that existing functionality continues to work after software changes.
After updating the checkout payment screen, test the new behavior and important existing checkout flows.
06 • Defect Reporting
Write actionable bug reports
A strong defect report gives the development team enough information to understand, reproduce, investigate, and resolve an issue.
Briefly explain the problem and where it occurs.
Include platform, browser, device, build, and environment.
Provide clear and repeatable numbered steps.
Describe what should have happened.
Describe what actually happened.
Include screenshots, videos, logs, or test data.
Checkout — Place Order button remains disabled after entering valid payment information.
07 • Practice
Design tests for a registration form
Imagine a registration form containing first name, last name, email, password, confirm password, and a Create Account button.
Write at least eight tests that include positive, negative, boundary, validation, and usability coverage.
08 • Knowledge Check
Check your understanding
Complete This Lesson
Finished reviewing Manual Testing Essentials and the knowledge check? Mark the lesson complete to save your progress.