Scribd
Upload
12 views

Regression Testing and Encapsulation

This document discusses regression testing and encapsulation. Regression testing involves retesting software after changes to ensure existing functionality was not broken and changes work as intended. It includes impact analysis, prioritizing test cases based on criticality and frequency of use, and focusing testing on areas like integration points and complex functionality. Encapsulation involves wrapping data and methods together within a class and controlling access via public methods to hide internal details and protect against changes breaking code. Benefits include flexibility to modify implementations without affecting other code and maintainability.

Uploaded by

appleusr2000
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
12 views

Regression Testing and Encapsulation

This document discusses regression testing and encapsulation. Regression testing involves retesting software after changes to ensure existing functionality was not broken and changes work as intended. It includes impact analysis, prioritizing test cases based on criticality and frequency of use, and focusing testing on areas like integration points and complex functionality. Encapsulation involves wrapping data and methods together within a class and controlling access via public methods to hide internal details and protect against changes breaking code. Benefits include flexibility to modify implementations without affecting other code and maintainability.

Uploaded by

appleusr2000
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9

REGRESSION TESTING

&
ENCAPSULATION

SUBMITED BY:

S. PORSELVI

P.NAVESHAPRITHINKRA
R.PRIYANGA
WHAT IS REGRESSION TESTING?
 Checking the product after changes.

TO ENSURE:

Changes work as designed.

Change does’nt break any existing functionalities.

 Follows selective retesting techniques.

 Impact analysis is done


WHEN TO DO IT
 Regression testing is required when there is a-

 Change in requirements and code is modified according to the


requirement.
 New feature is added to the software.
 No of defects have been fixed
 Performance issue fixed
 Planned Test Activity / Need based Activity

Why?
1. Defects fixes may cause existing functionality
2. New features may cause defect in one other features.
STEPS
Step1: Perform initial 'Smoke’ or ‘Sanity’ test.
Step2: Understand criteria for selecting test cause.
Step3: Classify test case based priority.
Step4: A methodology for selecting test cases.
Step5: Reselting Test case for test execution.
Step6: conclude the result.
PRIORITIZATION OF TEST CASES
Prioritize the test cases depending and business
impact, critical & frequently used functionalities. Selection of test
cases based on priority will greatly reduce the regression test suite.

AREA TO FOCUS DURING TESTING:


Test cases which have frequent defects.
Functionalities which are more visible to the users.
Test cases which verify core features of the product.
All integration test cases.
All complex test cases.
Boundary value test cases
Sample of successful test cases.
Sample of failure test cases.
PRO’S AND CON’S

Challenges for regression testing : Effective regression tests:


 With successive regression runs, test  Code being regression tested should be
suites become fairly large. Due to time under a configuration management tool.
and budget constraints, the entire  No changes must be allowed to code,
regression test suite cannot be executed.
during the regression test phase.
 Minimizing test suite while achieving Regression test code musdrt be kept
maximum test coverage remains a immune developer changes.
challenge.  The database used for regression testing
 Determination of frequency of must be isolated. No database changes
Regression Tests ie, after every must be allowed.
modification or every build update or
after a bunch of bug fixes, is a challenge.
ENCAPSULATION

 Encapsulation is the technique of making the fields in a class private and providing access to the fields via public methods.
 encapsulation also can be described as a protective barrier that prevents the code and data being randomly accessed by
other code defined outside the class.
 Wrapping up of data and methods into a single unit.

IMPORTANCE OF ENCAPSULATION:

 To Hide the internal implementation details of the class .


 Can safely modify the implementation without worrying breaking the existing code that uses the class.
 Protect class against the accidental willful stupidity.
 Keeps class tidy by keeping the visible fields to a minimum.
 Easier to use and understand.
Why need encapsulation ?
 Combining data and how its manipulated in one place:
 This is achieved through the state (the private fields ) and the behaviours (the public
methods)of an object.

 Only allowing the state of an object to be accessed and modified


through behaviours:
 The values contained within an objects state can then be strictly controlled.

 Hiding the details of how the object works:


 The only part of the object that is accessible to the outside world is its behaviours. What
happens inside those behaviours and how the state is stored is hidden from view.
BENEFITS:

 The main benefit of encapsulation is the ability to modify our implantation code without
breaking the code of others who use our code.

 With this feature encapsulation gives maintainability, flexibility and extensibility to the
code.

thank you

You might also like