Programming Homework Help

Testing Plan

Purpose :

This test plan describes the approach and overall framework that will guide the testing of Agree

.The document introduces:

● Test Strategy: the objectives, approach, assumptions of the test.

● Test Execution: how the test will be carried out, the expected input for and output of the test, how to identify errors, and how to fix those errors.

Test Strategy

Test Objectives The object of the test is to validate the application’s functionality and that it works as specified.The test will determine what works well and will identify, offer solutions to, fix, and retest all flaws in the minimum viable product.The test will produce a functional minimum viable product as specified in the project milestones, which includes:

● allowing a user to create a decision-based proposal with up to eight options to be voted on with ranked-choice voting 6

● setting a standard deadline of five minutes for all proposals to be voted on

● allowing up to 100 participants to vote

● displaying the resulting decision after certain conditions are met

Test Assumptions

The minimum viable product of the application will be complete.

Features To Be Tested

The initial testing will focus on the backend functionality of the application.This testing will also include a basic functionality of the user interface. Specifically, it will address how the user creates and submits a proposal within a specified deadline, how invited users view and interact with that proposal, and how all users view the results.These features are dictated by the minimum viable product.

Test Execution

Test Expectations

For successful testing of the application, the following inputs are expected:

● User creates a decision-based proposal sentence

● User creates a minimum of two options to the proposal to be voted on

● User submits the proposal via the submit button

● Invited users select and order their votes from the created proposal

● Invited users submit their votes via the submit button

With the above inputs, the following outputs are expected during testing:

● Notification of a successfully created proposal

● Notification of a unsuccessfully created proposal

● Notification of a successful vote for a proposal option

● Notification of an unsuccessful vote for a proposal option

● Notification that voting time for the proposal has ended

● Display of decision results to all users