4. TESTING

Developers or the people responsible for QA manually check individual components (functions, methods) by executing the code and verifying that each unit behaves as expected. This can be time-consuming and prone to human error since each test must be repeated for different inputs.

Example. A QA engineer manually tests the "add task" feature by entering various inputs and observing the output.

Automated tools (e.g., JUnit, Mocha) are used to run predefined test cases for each unit of code. These tests run quickly and can be triggered automatically with every code change, providing immediate feedback.

Example. Using Mocha to automatically test that the "add task" feature correctly adds tasks to a list for various input conditions.

Testers manually verify that different components of the system interact correctly by running through a series of test cases that simulate these interactions. This requires thorough documentation and multiple iterations to check data flow and function calls.

Example. A tester manually inputs a task into the front-end, verifies it reaches the database, and checks that it's retrieved and displayed properly on the interface.

Automated tools (e.g., Selenium, Postman) simulate interactions between components, such as making API calls to test communication between the front-end and back-end. These tests can automatically detect inconsistencies in how components work together.

Example. Using Postman to automatically send a request from the front-end to the back-end, then checking the database to confirm that the data is stored and retrieved correctly.

Those responsible for QA manually test the entire system in an environment that mirrors real-world usage. This might involve executing test cases that cover the entire app flow (e.g., login, add a task, mark it complete). Manual system testing is useful for catching subtle issues that might not be evident in automated tests.

Example. A person responsible for QA tests the entire app manually, logging in, adding a task, checking that it appears in the task list, and verifying data synchronization across the app.

Automated tools run full-system test cases to simulate user behavior across the entire application, ensuring all parts work together as intended. Automation helps cover a wide range of use cases quickly but may not catch all user interface or usability issues.

Example. Using Selenium to automate end-to-end tests, such as logging in, adding a task, and completing it to verify the full system process.

Real users manually test the system to see if it meets their needs and expectations. This process typically involves a beta test, where users explore the software and report any issues or feature requests. The feedback is then used to make final adjustments.

Example. A group of users manually test the app in a beta environment, adding tasks, completing them, and providing feedback on usability or missing features.

Although UAT is typically manual, some parts of the process can be supported by automated tools (e.g., collecting feedback, crash reports, or performance data during beta testing). Automated scripts might also gather specific metrics to evaluate performance.

Example. Automated tools track how users interact with the app during UAT and generate reports on performance or common failure points without requiring manual checks from the development team.