High Level-Regression Testing Notes PDF

Preview

Summary

Lecturer: T O'Kane
These are notes for the topic of Regression Testing...

Description

Types of Testing High Level Testing: -

Testing the product as a whole Usually performed by independent test group

High Level Test Cases: These test cases define the functionality of a software/product in a broader way without going into deep functionality. Like if we must write high level test cases for login functionality we'll test that 'User should be able to login success full with valid credentials'. Advantages: Its advantage is that a tester is not bound to follow the test cases step by step and thus it gives a chance to explore more edge cases. This also increases the chance to find new bugs. Disadvantages: Its disadvantage is that it’s not sure that all scenarios are covered and it’s difficult for an inexperienced tester to work with these test cases. 1. 2. 3. 4.

Types: Usability testing Function testing System testing Acceptance testing

1. Usability Testing: -

-

Answers question, how well does software adapt to users’ work styles, not the other way around Have users work on the product and observing their responses to it Done as early is possible for customer as more value is obtained Test criteria identified: o How easy is it for user to navigate? o How many mouse clicks to perform a function? Often concerned with presentation not functionality o User Experience Usability characteristics include: o Accessibility –  Ensure everyone can use it -> disabilities and impairments o Responsiveness o Efficiency o Comprehensibility

Note: Task knowledge - something you instinctively know because of knowledge of the system or process.

Types of Testing 2. Function Testing: -

-

Goal is to detect discrepancies between programs functional specification and its actual behaviour – Proposed vs actual If discrepancy is found o Is the program solution wrong? o Is the specification wrong? All black-box methods for function based testing are applicable Performed by independent testing group Begins: o Can begin when sufficient functionality is available – as early as possible o Can begin after unit or integration testing have been completed

3. System Testing: -

-

Despite name -> NOT testing the entire system Tries to show if the system does not meet original requirements and objectives Requirements or specification documents do not describe the system’s functions in precise terms NO methodology can be applied o Testers must use great deal of creativity o Thinking from the user’s perspective Approaches that can be used to system test: 1. Volume testing – can system handle required volumes of data 2. Stress testing – can system handle peak load conditions 3. Security testing – can system’s security be breached 4. Performance testing – can system meet performance needs 5. Resource usage testing – will system exceed its resource limits 6. Configuration testing – will system fail if differently configured 7. Other approaches i. Compatibility testing ii. Installability testing iii. Recovery testing iv. Serviceability testing v. Reliability testing vi. Availability testing

Vera Slattery Shot Paddy Running Clockwise

4. Acceptance Testing: -

Goal is to detect discrepancies in system’s behaviour in actual target environment Tests usually run by customers Run for pre-specified period which has to reflect o Longest functional response time  E.g. a system may have a function that takes 6 months  -> Acceptance test >= 6 month o Learning curve for new system

Types of Testing Other Types of Testing: Regression Testing: -

Most test cases rather than simply being discarded will become part of a regression suite A regression suite is a collection of all test that have been performed on the system so far to ensure it work properly If new feature is added to system, new system must undergo all tests (regression tests) in the regression suite to ensure the new functionality did not break existing functionality In many organisations, regression testing is automated and run off-peak, outside of business hours...