This software testing guide is the next in-line topic on what we discussed earlier. We have discussed a diverse set of topics, and spent quite a lot of time with the discussion of software development methodologies –agile,waterfall,scrum,v-model, etc. And with good reason.
Over the years, I have noticed how process and methodology play an important role in project success—sometimes it is so important to follow the right process, like having the right person for a job. You can hire the crème de la crème for your team, but it doesn't matter if you don't have a robust process to govern yourself during delivery.

What is Software Testing?
The internet defines software testing as the process of running a program or application with the intention of identifying errors. I define testing as a process of validation that a piece of software meets its business and technical requirements. Testing is the primary way to verify that the built product meets the requirements appropriately.


https://www.exltech.in/software-testing-course.html



Software Testing Procedures

Agile or waterfall, Scrum, or RUP, traditional or exploratory, there is a basic process of software testing. Let's look at the components that make up the whole.

1. Test strategy and test plan

Every project needs a test strategy and a test plan. These artifacts describe the test area for a project:

• The systems that need to be tested and all specific configurations
* The features and functions that are the focus of the project
• Non-functional requirements
* Test approach-traditional, explorative, automation, etc. - or a mixture
* Key processes to follow-for broken resolution, broken triage
* Tools for the detection of errors, for test case scripting, traceability
* Obtain documentation and produce as output
* Test environment requirements and setup
* Risks, dependencies and contingencies
* Test plan
* Approval workflows
* Entry /Exit Criteria

2.What do you mean?Test Design
Now that you have a strategy and a plan, the next step is to dive into a test-suite. A test Suite is a collection of test cases necessary to validate the built system against its original requirements.
Test-design as a process is a grouping of Test Manager experience with similar projects over the years, the testers knowledge of the system/functionality tested, and prevailing practices in the audit to a certain point. For example, if you're working for a company in the early stages of a new product development, your focus will be on detecting major errors with the alpha/beta versions of your software and less on making the software completely fail-safe.

3.Test execution
You can run tests in many different ways-as a single, waterfall-SIT (system integration test) and UAT (User Acceptance Test) phases; as part of Agile sprints; supplemented by exploratory testing; test-driven development. Ultimately, you must perform a sufficient amount of software testing to ensure that your system is (relatively) error-free.

4.Test Lock
Right—so you have made the planning necessary, carried out tests and now want your product to release green-light. You must consider the initial criteria for completing the test cycle and readiness for release. Let's look at the components of the initial criteria in general:
* 100% requirement coverage: all business and technical requirements must be covered by Tests.
* Minimum % pass rate: targeting 90% of all test cases to be passed is best practice.
* Fix all critical defects: self-explanatory. You're critical for one reason.

For more details:https://www.exltech.in