Level 4 Recap 3

Assignment Recap and Prep

Test Plans, Test Driven Development, and IDE features

Purpose of a Test Plan

• Define objectives and scope of testing

• Set out resources and requirements

• Scheduling

• Set out success criteria

Test Plan Structure

• Test objectives

• Test scope

• Test cases

• Outcomes and notes

Test plans should be

• Clear

• Repeatable

• Comprehensive

Multiple Choice

Which of these elements would not be on a test plan?

• Personal opinions
• Date and time

• Test objectives
• Dependencies

Reorder

What is the appropriate layout of a test plan?

• Objectives

• Scope

• Requirements

• Test Cases

• Outcome

1

2

3

4

5

• 1
• 2
• 3
• 4
• 5

Test objectives

• Highlights main aims of test

• Informs test case design

• Indicates the timeline of the test

• Should guide test-team

Test Scope

• Defines what is in scope - what features are being tested?

• Defines what (if anything) is not in scope

• Define integration requirements (if needed)

Test Cases

• Individual

• Many

• Simple

• Align to objectives and scope

Test Case Structure

​Test ID	Date/time	​Description	​Input Data	​Expected Output	​Actual Output	​Notes
​1	12/12/24 13:30	​Ensure valid username is accepted when signing up	​Username_123	​Sign up successful, next screen loads	​As expected	​
​2	​12/12/24 13:35	​Ensure invalid username (special char) is not accepted	​Username_123$	​User error message preventing page load, ask user to try again	​Username accepted and next page loaded	​Bug fix - invalid username allowed

Outcomes

• Define test outcome pass/fail

• Note any issues

• Suggest required action

• Sign off section

Scenario Questions

Login System

A small business wants to implement a login system for its website. The system requires users to enter a username and password to access their accounts. Below are the details of the login functionality:

• If the username and password are correct, the user is logged in.

• If the username is incorrect, the system shows an error message: "Invalid username."

• If the password is incorrect, the system shows an error message: "Invalid password."

• If the username or password fields are left blank, the system shows: "Fields cannot be empty."

Reorder

What is the appropriate order for executing a test plan for the scenario?

A small business wants to implement a login system for its website. The system requires users to enter a username and password to access their accounts. Below are the details of the login functionality:

If the username and password are correct, the user is logged in.

If the username is incorrect, the system shows an error message: "Invalid username."

If the password is incorrect, the system shows an error message: "Invalid password."

If the username or password fields are left blank, the system shows: "Fields cannot be empty."

• Define test case inputs and expected outputs

• Run test cases

• Compare actual output to expected

• Document results

1

2

3

4

• 1
• 2
• 3
• 4

Multiple Choice

What is the primary objective of the test plan for the login system, based on the requirements?

A small business wants to implement a login system for its website. The system requires users to enter a username and password to access their accounts. Below are the details of the login functionality:

If the username and password are correct, the user is logged in.

If the username is incorrect, the system shows an error message: "Invalid username."

If the password is incorrect, the system shows an error message: "Invalid password."

If the username or password fields are left blank, the system shows: "Fields cannot be empty."

• Verify the system accepts all input formats

• Ensure that users can register for the system

• Validate login system correctly identifies valid/invalid input

• Test design of the login page

Multiple Choice

What is the primary purpose of a test plan?

• To identify all possible bugs in a system.

• To document the testing scope, approach, resources, and schedule.

• To provide code-level documentation for developers.

• To automate the testing process.

Match

Match the test plan component with its description.

• Test Objectives

• Test Scope

• Test resources

• Exit criteria

What the testing is expected to achieve

What will and will not be tested

Tools and software required for testing

Requirements for testing to be complete

• What the testing is expected to achieve

• What will and will not be tested

• Tools and software required for testing

• Requirements for testing to be complete

Multiple Choice

Your team is testing a new e-commerce website. The team identifies that certain features will not be included in this test phase. Where should this information be documented in the test plan?

• Test Objectives

• Test Scope

• Exit Criteria

• Test Environment

Poll

What do you think is the most challenging aspect of creating a test plan?

• Defining clear and measurable test objectives.

• Determining the scope of testing and deciding what to include or exclude.

• Identifying all possible test cases, including edge cases.

• Writing detailed and understandable documentation for others to follow.

• Something else

Multiple Choice

Which software development approach make heavy use of test plans?

• Scrum

• Result driven development

• Test driven development

• Agile

Test Driven Development

TDD Approach

• Design tests first - running should fail

• Write code to pass defined tests

• Run tests

• Refactor

TDD

TDD Benefits

• Early error detection

• Improved code quality

• Easier maintenance/refactoring

• Improves collaboration

• Improved focus

• Facilitates automation

TDD Drawbacks

• More time up front

• Learning curve

• Over-testing trap

• Reliant on good tests

Multiple Choice

What is the main principle of Test-Driven Development (TDD)?

• Writing code and then creating tests for it.

• Writing tests before writing the actual code.

• Writing tests and code simultaneously.

• Only testing after the software is fully implemented.

Multiple Choice

TDD reduces debugging time because errors are identified early in the development process.

• True

• False

Drag and Drop

The three main steps to the TDD cycle are often called​

Placeholder

,​

Placeholder

and​

Placeholder

Drag these tiles and drop them in the correct blank above

red

green

refactor

amber

reuse

repeat

Match

Match the TDD cycle step to its description.

• Red

• Green

• Refactor

Write failing tests

Write just enough code to make the test

Improve the code without changing its be

• Write failing tests

• Write just enough code to make the test

• Improve the code without changing its be

Open Ended

In your own words, explain how TDD can lead to better code design.

IDE Key Features

Debugger

• Highly useful feature

• Allows control over code execution

• Lets you pause code

• View variable values

• Create watch expressions

• Track function calls

Version Control Integration

• Usually have built in support for version control (e.g. Git)

• Allows easy commits, branching, branch switching etc

• Often gives visual of branches

• Allows seamless linking to remote repos

Editor Features

• Syntax highlighting

• Error detection

• Autocomplete

Assignment Tips

Writing Style

• Write in formal style

  • Third person

  • Structured in sections

  • NOT by criteria

Layout

• Title

• Subtitles

• Name in header

• Page numbers

• Font - sensible style (Times New Roman or Arial is my suggestion)

• Align text - either justify or left

• Images or tables - ensure captioned

References

• In text citation - (Author Surname, Year)

  • (Smith, 2020)

• Reference list

  • Includes ALL in text citations

  • Alphabetical by author surname

• Suitable references

  • Text books

  • Journals

  • Websites with clear author, time and academic suitability

Criteria Tips and Required Evidence

P4 - Write a program that implements and algorithm using an IDE

• You need to design algorithms yourself - especially SORT

• Evidence will be

  • Code

  • Report (part)

• Discuss features of IDE used

• Screen shots can help

P5 - Explain the debugging process and the debugging facilities available in the IDE

• Refer to your own development - how did you debug?

• Explain common ways to approach debugging

• Explain how an IDE can be used for debugging

P6 - Explain the coding standard you have used in your code

• Identify coding standards you have implemented

• Explain what that means - why have you used it?

• Make it clear what the requirement of that standard are

M3 - Enhance the algorithm writtem, using the features of the IDE to manage the development process

• You will likely need to evolve your design - evidence this in your work

• Identify key features of the IDE that benefited this

  • Language specific features

  • Source control?

  • Debugger?

  • Etc

M4 - Examine how the debugging process can be used to help develop more secure, robust applications

• Analyse/breakdown the importance of debugging for this - explain how

• Secure does not mean anti-hacking

• No unexpected behavior

• Meets expectations and standards

• Robust - error handling, no crashes etc

D3 - Evaluate the use of an IDE for development of applications contrasted with not using an IDE

• Evaluate - use an analysis to make a judgement

• Breakdown the reasons, explain each one

• Discuss the benefits

• Discuss the impact

• Explain every point

D4 - Evaluate the role and purpose of a coding standard and why it is necessary in a team as well as for the individual

• Evaluate - use an analysis to make a judgement

• Breakdown the reasons, explain each one

• Ensure you discuss for TEAMS and INDIVIDUALS

• Bring all points back to WHY - benefit, impact etc