0% found this document useful (0 votes)
4 views3 pages

Milestone 7

The document outlines various test types including Unit, Integration, System, Acceptance, and Interactive testing, detailing their respective targets, inputs, and expected outputs. Each test type is designed to ensure different aspects of a program or system function correctly, such as user access, data integrity, and system performance under load. Specific scenarios are provided for each test type to illustrate the expected results based on given inputs.

Uploaded by

jahongir6701
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views3 pages

Milestone 7

The document outlines various test types including Unit, Integration, System, Acceptance, and Interactive testing, detailing their respective targets, inputs, and expected outputs. Each test type is designed to ensure different aspects of a program or system function correctly, such as user access, data integrity, and system performance under load. Specific scenarios are provided for each test type to illustrate the expected results based on given inputs.

Uploaded by

jahongir6701
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Test Types: Unit, Integration, System, Acceptance

Test Type Integration

Test Target Driver

Test Input Bool: True (modules run successful)

Expected Output The integration between modules run.

Test Type Interactive testing

Test Target Tutorial

Test Input Bool: True (login successfully)

Expected Output User is re-routed to the Employee Handbook,


or Customer Tutorial depending on the login
input.

Test Type Acceptance

Test Target Employee Handbook

Test Input Bool: True (means user is an employee)

Expected Output Handbook is successfully opened and closed


after use

Test Type Acceptance

Test Target Customer Tutorial

Test Input Bool: True (means user is a customer)

Expected Output Tutorial is successfully completed or aborted

Test Type Unit Testing

Test Target Program

Test Input Run the program to check any bugs and error
Expected Output Program without any bugs and error, and
shows properly

Test Type Interactive testing

Test Target Database

Test Input Click to view the data (already been


populated by orders)

Expected Output Verify that all data appears correctly

Test Type System Testing

Test Target Device

Test Input Sign in on different accounts with seperate


devices

Expected Output Correct data and functionality displayed and


interacted through multiple devices

Test Type Unit Testing

Test Target Raw Data

Test Input Check data if it is out of min or max range


and the normality of the raw data

Expected Output Raw data is not out of range and can be


handled by the program

Test Type Unit Testing

Test Target Calculated Data

Test Input Sends a mock order through data calculating


functions

Expected Output Correct statistics on popularity, fulfillment


times etc.
Test Type Interactive Testing

Test Target Access Level

Test Input Click everything on screen and see if you can


view the calculated data as a guest

Expected Output The calculated data will never appear if you


are signed in as a guest

Test Type Load Testing

Test Target Name

Test Input 1 + the max number of guests attempt to sign


in at once

Expected Output One of the guests will get a “Restaurant is


full” error

Test Type Unit Test - isValidManager(string username) :


bool

Test Target User Management component

Test Input “Coke_123” - User is not the registered


manager

Expected Output False

Test Type Unit Test - RemoveEmployee(string


employee, string username) : bool

Test Target User Management component

Test Input “ chef ”, “ John_22 “ - User is a registered


chef

Expected Output True

You might also like