To check for the bug fixes. And this fix should not disturb other functionality

To guarantee the newly added functionality or existing modified functionality or developer fixed bug come up with any new bug or affecting any other side effect. this is called regression test and ensure already PASSED TEST CASES would not arise any new bug.

A page is not often accessed, or some activity is executed rarely but that thing outputs some essential Data wrongly, or corrupts the data, this will be a bug of H severity L priority

Use risk analysis to decide where testing should be focused. Since it’s not often possible to test every possible portion of an software/application, every probable combination of events, every dependency, or everything that could go wrong, risk analysis is suitable to most software development projects. This involve judgment skills, common sense, and experience.

Considerations can include:

Which functionality is most chief to the project’s intended purpose?
Which functionality is most visible to the user?
Which functionality has the largest safety impact?
Which functionality has the largest financial impact on users?
Which aspects of the application are most important to the customer?
Which aspects of the application can be tested early in the development cycle?
Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
Which aspects of similar/related previous projects caused problems?
Which aspects of similar/related previous projects had large maintenance expenses?
Which parts of the requirements and design are unclear or poorly thought out?
What do the developers think are the highest-risk aspects of the application?
What kinds of problems would cause the worst publicity?
What kinds of problems would cause the most customer service complaints?
What kinds of tests could easily cover multiple functionalities?
Which tests will have the best high-risk-coverage to time-required ratio

Normally test engineers concerned from entire test life cycle i.e, test plan, test case preparation, execution, reporting. Generally system testing, regression testing, adhoc testing etc.

In Any company apart from the small company Business analyst prepares the use cases. But in small company Business analyst prepares along with team lead.

Usually test engineers uses 4 types of methodologies

Boundary value analysis
Equivalence partition
Error guessing
Cause effect graphing

If we test whether defect is closed or not i.e Retesting But here we are checking the impact also regression means repeated times

Automated Testing

Advantages

It boost the efficiency of testing process speed in process
reliable
Flexible

Disadvantages
Tools should have compatibility with our development or deployment tools need lot of time at first If the necessities are changing endlessly then Automation is not suitable

Manual Testing

Advantages
If the requirements are changing endlessly Manual is suitable Once the build is stable with manual testing then only we go 4 automation

Disadvantages
Time Consuming
We can not do some type of testing manually
E.g Performances

Project Developed for specific client necessities are defined by client. Product developed for market necessities are defined by company itself by conducting market survey.

Example
Project:the shirt which we are interested stitching with tailor as per our specifications is project

Product:Example is “Ready made Shirt” where the particular company will imagine particular measurements they made the product
Mainframes is a product
Product has many no of versions
but project has fewer versions i.e depends upon change request and enhancements

Brain Storming
A learning technique involving open group discussion intended to expand the range of available ideas.
Brainstorming is a highly planned process to help make ideas. It is based on the principle that you cannot generate and calculate ideas at the same time. To use brainstorming, you must first gain agreement from the group to try brainstorming for a fixed interval (eg six minutes).

Cause Effect Graphing
A testing technique that aids in selecting, in a systematic way, a high-yield set of test cases that logically relates causes to effects to produce test cases. It has a beneficial side effect in pointing out incompleteness and ambiguities in specifications.