Matthew Bugenhagen’s Post

Unit Testing is a software testing technique where individual components or units of code are tested in isolation to ensure they function correctly. The primary goal of unit testing is to validate that each unit of the software performs as expected, thereby identifying and fixing bugs at the earliest possible stage in the development cycle.

The article where I discuss software testing processes is published on Medium. 1. Testing Principles. 2. Software Testing Process. 3. Functional and Non-Functional Testing. 4. Manual and Automation Test. #SoftwareTest https://lnkd.in/dYpTUhuM

2 Truths of Software Testing 1. No application is ever bug free before testing.   2. No application is completely free of bugs, even after testing.

The Dos and Don'ts of Software Testing. Dos: 1. Always plan and design the testing process before starting to test. 2. Check that the test environment has been configured and set up correctly. 3. Reduce time and boost productivity by using automation tools. 4. Focus on testing the critical areas of the application first. 5. Perform regression testing after making any changes to the application. Don'ts: 1. Don't assume that the application is bug-free just because it looks good on the surface. 2. Don't skip any testing phases or exploratory testing processes. 3. Don't perform tests without proper documentation or test cases. 4. Don't rely solely on Automation testing. 5. Don't forget to test for performance, security, and compatibility issues. hashtag #Copied by Hijaz Abbas

One of the most confusing concept in Software Testing is SMOKE VS SANITY Testing. Smoke Testing is quickly checking the basic functionality of application under test is working as expected. Sanity Testing is checking if newly Added feature to the Application works as expected or a bug is fixed.

The Dos and Don'ts of Software Testing. Dos: 1. Always plan and design the testing process before starting to test. 2. Check that the test environment has been configured and set up correctly. 3. Reduce time and boost productivity by using automation tools. 4. Focus on testing the critical areas of the application first. 5. Perform regression testing after making any changes to the application. Don'ts: 1. Don't assume that the application is bug-free just because it looks good on the surface. 2. Don't skip any testing phases or exploratory testing processes. 3. Don't perform tests without proper documentation or test cases. 4. Don't rely solely on Automation testing. 5. Don't forget to test for performance, security, and compatibility issues. hashtag #Copied by Hijaz Abbas

🔺 QA Terminology Test. #6.🔺 What is Test Coverage in the context of software testing? Answers: A. This is the number of times a test case has been run to test a program. B. This is the percentage of successful tests out of the total number of tests. C. This is a measure of which parts of the program code have been tested and which have not been tested. D. This is the total number of test cases developed to test the program.

Common distribution / allocation of test cases among different types of testing wrt common best practices: 1. **Unit Testing**: 70-80% - Focuses on individual components or units of code. - Typically the largest portion because it ensures that each piece of the application works correctly. 2. **Integration Testing**: 10-15% - Verifies that different modules or services used by your application work well together. - Important for catching issues that arise from the interaction between integrated components. 3. **System Testing**: 5-10% - Checks the complete and fully integrated software product to evaluate its compliance with the requirements. - Ensures the system as a whole works as expected. 4. **Acceptance Testing**: 1-5% - Conducted to determine if the requirements of a specification or contract are met. - Usually the final testing phase, performed by the end users to validate the system's functionality. These percentages are guidelines and can be adjusted based on the specifics of the project, risk factors, and the criticality of different parts of the system.

Here's how a bug travels during software testing:

API Testing: APIs are like the connectors that allow different software systems to communicate and exchange data with each other. API testing is a type of software testing that involves testing application programming interfaces (APIs) directly and as part of integration testing to determine if they meet expectations for functionality, reliability, performance, and security.