Best Practices While Testing

Follow these steps while testing a system:

1. Prepare comprehensive test plan specifications and test cases for each level of testing. Supplement these with the test data and test logs. Test plans for system testing may involve operators and test plans because acceptance testing involves customers.

2. Design the test cases to test system restrictions, such as file and database size (stress testing).

3. Develop the data to test specific cases. Copies of live files must not be used except for Acceptance testing.

4. Do not use confidential data for testing without written authorization, especially in the case of Acceptance testing.

5. Follow relevant standards.

6. Perform Regression testing on each component of the system. This ensures that no anomalies have crept into the system because of the changes made to the system.

7. Make sure to document and set up the test environment for each level in advance of testing. Test environments specify the preconditions required to perform the tests.

8. Specify the intended test coverage as part of the test plan. Test coverage is the degree to which specific test cases address all specified requirements for a specific system or component.

Regards,

Pavankumar Nandagiri....

General Defect Management

Regards,

PavanKumar Nandagiri..........

Breadcrumbs

Breadcrumbs or breadcrumb trails are a navigation technique used in user interfaces.
Its purpose is to give users a way to keep track of their location within programs or documents. The term is taken from the trail of breadcrumbs left by Hansel and Gretel in the popular fairytale.


In Websites:

Breadcrumbs typically appear horizontally across the top of a webpage, usually below any title bars or headers. They provide links back to each previous page that the user navigated through in order to get to the current page, for hierarchical structures usually the parent pages of the current one. Breadcrumbs provide a trail for the user to follow back to the starting/entry point of a website. They may look something like this:

Home page → Section page → Subsection page


Regards,

PavanKumar Nandagiri..........

REGRESSION TEST

Regression test case selection methodology:

1.Code Base Regression Test Selection (CBRTS)
2. Specification Based Regression Test Selection (SBRTS)
3. Risk Based Regression Test Selection (RBRTS)

Regression test Folder Structure:

Module Level structure (Just with Modules)
1. Easy to Add
2. Easy to locate in high level
3. Easy to maintain in high level

UC level structure under Module (Existing structure of System Tests)

1.Easy to maintain in functional level / module level
2. Easy to locate in low level
3. Easy to maintain in low level

Regression test selection from System tests:

1.Risk Based Tests from every UC.
2. Test case that covers the primary objective / summary outline of the UC.
3. Test case that covers the priority E2E functionalities from that UC.
4. Integrated E2E test cases from UC level.

Conditions to be followed on Regression Test selection:

1. Selected tests must cover all the major functionalities of the module.
2. No –ve tests in RT.
3. Selected tests must not concentrate on data type / data change / screen design.
4. Selected tests must not get affected on DBCR/UICR.
5. Selected Regression tests must cover most of the UAT cases.
6. Selected tests must cover all the possible High Risk areas in functional flow.

Regards,

Pavankumar Nandagiri........