Question

Question 1

Why is testing important?

Question 2

What are the 4 different types of testing activities? What is the purpose of each type?

Question 3

What is the Waterfall methodology?

Answer 1

Why is testing important?

The following are the importance of testing for example software testing as it is assumed as nothing is mentioned in the question.

• Testing should be introduce in the early stage of the SDLC, The cost of fixing the bug is larger if testing is not done in early stage & bugs found in later stages.
• In the today’s competitive market only the quality product stays longtime firmly, so to make sure the produce the good quality product the testing of application is key factor in SDLC.
• As it not possible makes it software application is defect free but testing will be necessary.
• Most important thing of testing is the development environment is different than the Testing environment and the testing done on testing environment is similar to the Production environment.

After all for growth of any business the most important user satisfaction & testing plays a key role in to make this happen. But to make this happen we have to plan it properly before executing it. So proper test planning is required to make the system work effectively and more efficiently.

What are the 4 different types of testing activities? What is the purpose of each type?

The following are the different types of testing based on the software implementation which are briefly described below:

1.Unit tests:Unit tests are very low level, close to the source of your application. They consist in testing individual methods and functions of the classes, components or modules used by your software.

Purpose : Unit tests can be run very quickly by a continuous integration server.

2.Integration tests:Integration tests verify that different modules or services used by your application work well together. For example, it can be testing the interaction with the database or making sure that microservices work together as expected.

Purpose:These tests are very expensive and it is done in order to check whether the different multiple applications can be run .

3.End-to-end tests:End-to-end testing replicates a user behavior with the software in a complete application environment. It verifies that various user flows work as expected and can be as simple as loading a web page or logging in or much more complex scenarios verifying email notifications, online payments, etc...

Purpose :It is also very expensive when it is automated.So it is recommended to have few key end to end tests and rely on lower level testing to identify the breaking chnages which are needed in a system implementation and support.

4.Acceptance testing:Acceptance tests are formal tests executed to verify if a system satisfies its business requirements. They require the entire application to be up and running and focus on replicating user behaviors

Purpose:It can measure the performance of the system and reject whatever changes to be made if the goals set are not met with.

What is the Waterfall methodology?

The Waterfall Methodology

Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like:

1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance testing (UAT)
6. Fix any issues
7. Deliver the finished product

So in a Waterfall development project, each of these represents a distinct stage of software development, and each stage generally finishes before the next one can begin. There is also typically a stage gate between each; for example, requirements must be reviewed and approved by the customer before design can begin.