Contents
Introduction....................................................................................................................................................................1
Selection of Testing Methodologies.................................................................................................................................2
Unit Testing..................................................................................................................................................................2
Integration Testing.......................................................................................................................................................2
System Testing............................................................................................................................................................2
Functional Testing........................................................................................................................................................2
Test case.........................................................................................................................................................................2
Unit testing.....................................................................................................................................................................4
Integration Testing........................................................................................................................................................12
System Testing..............................................................................................................................................................18
Functionality testing.....................................................................................................................................................24
Analysis of Test Results and Communication................................................................................................................28
Overview of Test........................................................................................................................................................28
What Went Well.........................................................................................................................................................30
What Didn’t Go Well and How I Fixed It.....................................................................................................................30
Recommended Improvement....................................................................................................................................31
Communication with Development Team..................................................................................................................32
Introduction
I recently started working as a Software Test Engineer at a startup developing a new software product. The
,Selection of Testing Methodologies
To ensure the software product is robust, reliable, and meets client expectations, I have chosen a mixed approach
using multiple testing methodologies. These have been selected based on the type of system being tested and the
typical needs of end users, such as accuracy, usability, and stability.
Unit Testing
Unit Testing is a type of software testing where individual units or components of a software are tested. The goal is
to ensure that each unit of the software code performs as expected. Unit testing is performed by developers during
the development (coding phase) of an application. Unit Tests isolate a section of code and verify its correctness. The
reason I have chosen to do this testing is because housing sales program contains several distinct functions that can
be tested independently; therefore, it would be helpful on identify logical or syntactical errors in each function before
integration.
Integration Testing
Integration testing is the process of testing the interface between two software units or modules. It focuses on
determining the correctness of the interface. The purpose of integration testing is to expose faults in the interaction
between integrated units. I will be doing this testing once individual functions are tested or( unit testing is done).
This type of test will ensure smooth transitions between user actions, example viewing a property and then
purchasing it and it helps verify that user inputs and outputs transfer correctly between different stages.
System Testing
System testing is a type of software testing that evaluates the overall functionality and performance of a complete
and fully integrated software solution. It tests if the system meets the specified requirements and if it is suitable for
delivery to the end-users. This type of testing is performed after the integration testing. I have chosen this type of
testing because it validates the overall workflow from the user selecting a menu option to completing a transaction,
meaning it will ensure that all the functions including viewing, searching and purchasing operate without
interruption in one go.
Functional Testing
,Test Type Description of test Expected Out come
Unit . In this test I will be verifying the return The current houses for sale
stock function correctly displays the list are printed to the console,
of houses. This test will check that the with each house's details
function outputs the house details in the displayed as region, house
expected format (Region - House Type - type, bedrooms and cost.
Bedrooms - Cost).
Unit Next I will be testing the return stock A list of unique regions is
function to ensure it returns only unique printed to e.g., LONDON,
region names. This test verifies that the CARDIFF, LEEDS, and
function processes list and extracts a list BRISTOL.
of region names without any duplicates.
Unit I will be also testing that the fee The final total is
calculation for properties priced below calculated, and output
the £100,000 threshold works as it should be formatted as
should. This test checks if the 3% flat currency
fee is applied correctly when the
property price is less than or equal to
£100,000.
Unit Finally test in the house sale fee The final total is
calculation for properties priced above calculated, and the output
the £100,000 threshold is done. This test should be formatted as
verifies that the tiered fee structure 3% currency.
on the first £100,000 and 2% on the
remainder is applied correctly.
, houses located in that region is
displayed .
Integration This test verifies that after a sale The sale is recorded, and show
is completed using house sale, sales displays the sale details in
the sale details are stored and the format forename surname
can be retrieved and displayed and property cost total.
correctly using show sales.
Test Type Description of test Expected Out come
System The first system testing is to see The program correctly records
if the system complete end-to- the sale, calculates the final total
end sale process from menu and displays the formatted
selection to output. This test summary to the user.
simulates a user performing a full
sale transaction, ensuring that all
steps (selecting the sale option,
entering data, calculating the
total) function correctly together.
System Verify that the program handles The program displays user-
an invalid input in the house sale friendly error messages for each
process. This test checks the type of invalid input, and
program's robustness by prompts the user to enter valid
providing incorrect data and data
ensuring it responds with
appropriate error messages and
prevents the sale from
proceeding.
Test Type Description of test Expected Out come
Functional Verify the complete process of The program displays a sale
recording a sale with correct data summary and indicates the
and checking the summary transaction is complete.
output.
Introduction....................................................................................................................................................................1
Selection of Testing Methodologies.................................................................................................................................2
Unit Testing..................................................................................................................................................................2
Integration Testing.......................................................................................................................................................2
System Testing............................................................................................................................................................2
Functional Testing........................................................................................................................................................2
Test case.........................................................................................................................................................................2
Unit testing.....................................................................................................................................................................4
Integration Testing........................................................................................................................................................12
System Testing..............................................................................................................................................................18
Functionality testing.....................................................................................................................................................24
Analysis of Test Results and Communication................................................................................................................28
Overview of Test........................................................................................................................................................28
What Went Well.........................................................................................................................................................30
What Didn’t Go Well and How I Fixed It.....................................................................................................................30
Recommended Improvement....................................................................................................................................31
Communication with Development Team..................................................................................................................32
Introduction
I recently started working as a Software Test Engineer at a startup developing a new software product. The
,Selection of Testing Methodologies
To ensure the software product is robust, reliable, and meets client expectations, I have chosen a mixed approach
using multiple testing methodologies. These have been selected based on the type of system being tested and the
typical needs of end users, such as accuracy, usability, and stability.
Unit Testing
Unit Testing is a type of software testing where individual units or components of a software are tested. The goal is
to ensure that each unit of the software code performs as expected. Unit testing is performed by developers during
the development (coding phase) of an application. Unit Tests isolate a section of code and verify its correctness. The
reason I have chosen to do this testing is because housing sales program contains several distinct functions that can
be tested independently; therefore, it would be helpful on identify logical or syntactical errors in each function before
integration.
Integration Testing
Integration testing is the process of testing the interface between two software units or modules. It focuses on
determining the correctness of the interface. The purpose of integration testing is to expose faults in the interaction
between integrated units. I will be doing this testing once individual functions are tested or( unit testing is done).
This type of test will ensure smooth transitions between user actions, example viewing a property and then
purchasing it and it helps verify that user inputs and outputs transfer correctly between different stages.
System Testing
System testing is a type of software testing that evaluates the overall functionality and performance of a complete
and fully integrated software solution. It tests if the system meets the specified requirements and if it is suitable for
delivery to the end-users. This type of testing is performed after the integration testing. I have chosen this type of
testing because it validates the overall workflow from the user selecting a menu option to completing a transaction,
meaning it will ensure that all the functions including viewing, searching and purchasing operate without
interruption in one go.
Functional Testing
,Test Type Description of test Expected Out come
Unit . In this test I will be verifying the return The current houses for sale
stock function correctly displays the list are printed to the console,
of houses. This test will check that the with each house's details
function outputs the house details in the displayed as region, house
expected format (Region - House Type - type, bedrooms and cost.
Bedrooms - Cost).
Unit Next I will be testing the return stock A list of unique regions is
function to ensure it returns only unique printed to e.g., LONDON,
region names. This test verifies that the CARDIFF, LEEDS, and
function processes list and extracts a list BRISTOL.
of region names without any duplicates.
Unit I will be also testing that the fee The final total is
calculation for properties priced below calculated, and output
the £100,000 threshold works as it should be formatted as
should. This test checks if the 3% flat currency
fee is applied correctly when the
property price is less than or equal to
£100,000.
Unit Finally test in the house sale fee The final total is
calculation for properties priced above calculated, and the output
the £100,000 threshold is done. This test should be formatted as
verifies that the tiered fee structure 3% currency.
on the first £100,000 and 2% on the
remainder is applied correctly.
, houses located in that region is
displayed .
Integration This test verifies that after a sale The sale is recorded, and show
is completed using house sale, sales displays the sale details in
the sale details are stored and the format forename surname
can be retrieved and displayed and property cost total.
correctly using show sales.
Test Type Description of test Expected Out come
System The first system testing is to see The program correctly records
if the system complete end-to- the sale, calculates the final total
end sale process from menu and displays the formatted
selection to output. This test summary to the user.
simulates a user performing a full
sale transaction, ensuring that all
steps (selecting the sale option,
entering data, calculating the
total) function correctly together.
System Verify that the program handles The program displays user-
an invalid input in the house sale friendly error messages for each
process. This test checks the type of invalid input, and
program's robustness by prompts the user to enter valid
providing incorrect data and data
ensuring it responds with
appropriate error messages and
prevents the sale from
proceeding.
Test Type Description of test Expected Out come
Functional Verify the complete process of The program displays a sale
recording a sale with correct data summary and indicates the
and checking the summary transaction is complete.
output.
