TESTING DOCUMENT

Document Information :
Title : Input Request name as Title

Version No. : 1.0

Date Created : November 24, 2022

Date Updated : September 21, 2022

Document Author(s) : Author’s Name

 TESTING DOCUMENT* : Input Request name as Title * Ver. 1.0

Document Information

Document History
Ver Date Author
1.0 November 24, 2022 Author’s Name

Reviewer(s)
Position Name Signature
Project Manager Input nama project manager Tanda tangan PM
Team Leader Input nama project leader Tanda tangan TL
Technical Writer Author’s Name *

Approver(s)
Position Name Signature

Related Document
Doc. Ver Doc. Date Doc. Author Document Name
Isi Isi dengan Isi dengan nama Isi dengan nama dokumen yang berkaitan. Cth
dengan nama dokumen yang Dokumen User Requirement, dll
versi dokumen berkaitan. Cth
dokumen yang Dokumen User
yang berkaitan. Requirement, dll
berkaitan. Cth
Cth Dokumen
Dokumen User
User Requireme
Requirem nt, dll
ent, dll
 TESTING DOCUMENT* : Input Request name as Title * Ver. 1.0

Table of Contents*
DOCUMENT INFORMATION......................................................................................................... 2
TABLE OF CONTENTS*................................................................................................................ 3
1. INTRODUCTION..................................................................................................................... 1
1.1. PROCESS TESTING INFORMATION........................................................................................ 1
2. TEST CASE SCENARIO......................................................................................................... 1
2.1. FITUR YANG DI TEST (CTH. LOGIN)......................................................................................1
 TESTING DOCUMENT* : Input Request name as Title * Ver. 1.0

1. Introduction
This document contains the steps for testing tulis fitur yang di test. The type of testing
performed is the User Acceptance Test (UAT). This test will be carried out by the entire
Quality Assurance (QA) team.

This document is used as a basis for:

1. Determining the type and scope of the test.
2. Determine the Time, Place, and implementation of the test.
3. Define the scenario steps in the implementation of the test.
4. Perform Testing.
5. Check that the web application that has been built is in accordance with the design
and is running well.

1.1. Process Testing Information

The test execution will perform the following activities:
1. Manage the progress of the test execution
2. Tests are executed based on the test cases in this document
3. During the Stabilize phase, additional customer witnesses may attend the test
process
4. Test issues are logged centrally in a standard format
5. Test report will be provided to the client on completion

General strategy for the testing process shall be as described below:

1. Testing shall be conducted manually using functional black box testing.
2. Issues discovered during this stage shall be recorded in issue tracking system.
3. Testing shall again be done after defects have been fixed.

1
 TESTING DOCUMENT* : Input Request name as Title * Ver. 1.0

2. Test Case Scenario

This section describes about set of actions performed on a system to determine if it satisfies software requirements and functions
correctly. The purpose of a test case scenario is to determine if different features within a system are performing as expected and to
confirm that the system satisfies all related standards, guidelines and customer requirements. The process of writing a test case can
also help reveal errors or defects within the system.

2.1. Fitur yang di test (Cth. Login)

Test Scenario : Verify login

Expected Test UAT Notes
No Test Steps Capture
Result Result Result
Test case : User entered valid username and password
Search URL :
1. Displays Choose Choose
1. Go to Dashboard an item.
address an item.
after login
https:
localhost

1
 TESTING DOCUMENT* : Input Request name as Title * Ver. 1.0

Test Scenario : Verify login

Expected Test UAT Notes
No Test Steps Capture
Result Result Result
Login :
2. Choose Choose an
1. Input an item.
Username item.
2. Input
Password
3. Click Login
Button

Page will be
3. Choose Choose an
redirect to
an item.
item.
Dashboard

2
 TESTING DOCUMENT* : Input Request name as Title * Ver. 1.0

Test Scenario : Verify login

Expected Test UAT Notes
No Test Steps Capture
Result Result Result
Test case : User entered invalid username and password
Search URL :
1. If your Choose Choose an
1.Go to username an item. item.
address or
password
https:
are
localhost incorrect,
you will not
Login : be logged
2. Choose Choose an
1. Input in to the
an item. item.
Username page
2. Input because
Password web has
3. Click Login validation
Button for login.

3. Show Choose Choose an

notification an item. item.