SE401 · Annotated SlidesTesting throughout the SDLC — Testing throughout the Software Development Life Cycle
Testing throughout the SDLC · Annotated slides

Testing throughout the Software Development Life Cycle

Verification vs. validation, the V-model and iterative models, the test levels (component, integration, system, acceptance) with their objectives, test basis and typical defects, the test types (functional, non-functional, structural, change-related), and maintenance testing.

Slide text Study notes Highlight: key words Tips, tricks & traps Seen again elsewhere How it can come up
Slide 1: Slide 1
Exam weight Low
    Slide 2: • Software development models • Test Levels
    Exam weight Low
      Slide 3: • Testing is important in the software development life cycle • The life cycle model will determine how to organize the testing
      Exam weight Low
        Slide 4: • Verification
        Exam weight High
        1. Verification: "Are we building the product RIGHT?" (meets its specification). Validation: "Are we building the RIGHT product?" (meets users’ needs).
        TipVerification: "Are we building the product RIGHT?" (meets its specification). Validation: "Are we building the RIGHT product?" (meets users’ needs).
        🎯 How this can come up · 1 question
        MCQ

        "Are we building the right product?" is:

        Slide 5: Slide 5
        Exam weight Low
        1. V-model: each development phase on the left has a matching test level on the right (requirements ↔ acceptance, design ↔ system/integration, code ↔ component).
        Slide 6: Slide 6
        Exam weight Low
          Slide 7: • Testing needs to begin as early as possible in the life cycle. • Testing can be integrated into each phase of the life cycle.
          Exam weight Low
          1. Testing should begin as early as possible: reviews of requirements and designs find defects when they are cheapest.
          Slide 8: Slide 8
          Exam weight Low
            Slide 9: • In any life cycle model, there are several characteristics of good testing:
            Exam weight Low
              Slide 10: Slide 10
              Exam weight Low
                Slide 11: • Acceptance : is the responsibility of the customer – in general. The goal is to gain confidence in the system
                Exam weight Low
                  Slide 12: • For each test level, please note:
                  Exam weight Low
                    Slide 13: • Verifying the functioning of software items (modules, methods, objects, classes etc.) that are separately testable
                    Exam weight Low
                    1. Component (unit) testing: individual components in isolation, usually by developers, often with stubs and drivers.
                    Slide 14: • All materials that are applicable for the component under test:
                    Exam weight Low
                      Slide 15: • Writing code to test the project code • Stubs, drivers and simulators may be used.
                      Exam weight Low
                        Slide 16: Slide 16
                        Exam weight Low
                          Slide 17: • Component testing usually involves the programmer who wrote the code.
                          Exam weight Low
                            Slide 18: • Tests interfaces between components
                            Exam weight Low
                            1. Integration testing: interfaces and interactions between components (component integration) or systems (system integration).
                            Slide 19: • Software and system design • The system architecture
                            Exam weight Low
                              Slide 20: • The item under test includes
                              Exam weight Low
                                Slide 21: • Component integration
                                Exam weight Low
                                  Slide 22: • Start integration with those components that are expected to cause most problems.
                                  Exam weight Low
                                    Slide 23: • Testing the behavior of the whole system as defined by the scope of the project.
                                    Exam weight Low
                                    1. System testing: the behaviour of the whole system against the requirements, in an environment close to production.
                                    Slide 24: • System requirements specification , both functional and non functional • Business processes
                                    Exam weight Low
                                      Slide 25: • The entire integrated system • User manuals
                                      Exam weight Low
                                        Slide 26: ee
                                        Exam weight Low
                                          Slide 27: • The questions to be answered:
                                          Exam weight Low
                                            Slide 28: • User requirements specification • Use cases
                                            Exam weight High
                                            1. Acceptance testing: establish confidence that the system is fit for use: user acceptance, operational, contract and regulation, alpha and beta.
                                            🎯 How this can come up · 1 question
                                            MCQ

                                            Testing against contract requirements before the customer signs off is:

                                            Slide 29: • User acceptance testing – validate the fitness for use of the system by users.
                                            Exam weight Low
                                              Slide 30: • Contract and regulation acceptance testing performed against a contract’s acceptance criteria (i.e. governmental, legal or safety
                                              Exam weight Low
                                                Slide 31: • Customers or users of a system • Stakeholders may be involved
                                                Exam weight Low
                                                  Slide 32: Slide 32
                                                  Exam weight Low
                                                  1. Functional testing: WHAT the system does. Non-functional: HOW WELL (performance, load, usability, security, reliability).
                                                  Slide 33: • Objectives
                                                  Exam weight Low
                                                    Slide 34: • Objectives
                                                    Exam weight Low
                                                      Slide 35: Slide 35
                                                      Exam weight Low
                                                        Slide 36: • Objectives
                                                        Exam weight Low
                                                          Slide 37: • Test basis
                                                          Exam weight Low
                                                            Slide 38: • Confirmation testing
                                                            Exam weight High
                                                            1. Confirmation testing (re-testing): check that a fixed defect is really fixed. Regression testing: check that the change broke nothing else.
                                                            Exam trapRe-testing confirms the FIX; regression testing looks for SIDE EFFECTS.
                                                            🎯 How this can come up · 1 question
                                                            MCQ

                                                            Running the failed test again after a bug fix is:

                                                            Slide 39: • Objective
                                                            Exam weight Low
                                                              Slide 40: • Approach
                                                              Exam weight Low
                                                                Slide 41: • Objectives
                                                                Exam weight Low
                                                                1. Maintenance testing: triggered by modifications, migration or retirement of a live system; includes impact analysis and regression testing.
                                                                Slide 42: • Modifications
                                                                Exam weight Low
                                                                  Slide 43: • Scope
                                                                  Exam weight Low
                                                                    Slide 44: • Approach
                                                                    Exam weight Low