1 of 42

Final Project

​

“Resonance Ticketing System”

— Web UI & API Testing

Selvia

2 of 42

Education

Selvia Tunjungsih

S1 Informatika - UMS

Simple automation testing for saucedemo website using

selenium and testng

Saucedemo Automation Testing using Selenium

API testing for Sport Reservation using

Rest Assured and Postman

Sport Reservation API Testing

Working Experience

SQA - Formulatrix Salatiga (2023 - 2025)

Overview Mini Project

UI & API testing for RTS platform using Selenium and

Rest Assured

Resonance Ticketing System

3 of 42

4 of 42

Problem Statement

5 of 42

Resonance Ticketing System

​

Resonance → platform web untuk pelaporan & manajemen tiket issue. Pengujian dilakukan untuk memastikan alur pelaporan dan respons API berjalan dengan benar.

​

Scope:

  • Web UI end-to-end testing (feature: Register, Login, Create Ticket, Sorting/Filter)
  • Compatibility testing (Chrome & Firefox)
  • API testing
  • Test execution using Selenium and Rest Assured

​

Tujuan Pengujian:

  1. Memvalidasi fungsionalitas utama.
  2. Menjamin response API sesuai spesifikasi (status code & payload).
  3. Mendeteksi bug fungsional sedini mungkin.

​

Alasan Pengujian → Menjamin stabilitas sistem dan akurasi data agar proses pelaporan berjalan lancar dan dapat diandalkan.

6 of 42

Requirement & Test Plan

7 of 42

Test Plan

​

​

8 of 42

9 of 42

10 of 42

11 of 42

12 of 42

Full Test Plan can be accessed on:

Full Test Plan Document

​

​

13 of 42

Manual Testing

14 of 42

Test Cases

15 of 42

BUG REPORT

bug report

​

16 of 42

Full Test Cases & Manual testing can be accessed on :

​

Full Test Cases Document

17 of 42

Automation Testing

18 of 42

UI Testing

​

url: https://resonance.dibimbing.id/

​

tools: Selenium, testng, gradle

​

feature yang diuji:

  • Ticket Creation
  • Login
  • Registration
  • Sorting/Filtering

​

​

19 of 42

UI Testing

​

​

​

Struktur Folder

​

​

​

​

20 of 42

Element locator

​

​

​

21 of 42

Method

​

​

​

22 of 42

Assertion

​

​

​

23 of 42

Logging

​

​

​

24 of 42

Report

​

​

​

Extent-report

​

​

​

testng

​

​

​

25 of 42

API Testing

​

url: https://resonance.dibimbing.id/docs

​

tools: Rest Assured, testng, gradle

​

feature yang diuji:

  • /api/rest/login
  • /api/rest/createTicket
  • /api/rest/ticketById
  • /api/rest/updateStatusTicket
  • /api/rest/deleteTicket
  • /api/rest/myTickets

​

​

26 of 42

API Testing

​

​

​

Struktur Folder

​

​

​

​

27 of 42

Method

​

​

​

28 of 42

Body

​

​

​

29 of 42

Report

​

​

​

30 of 42

Load Testing

​

url: https://resonance.dibimbing.id/docs

​

tools:Jmeter

​

feature yang diuji:

  • /api/rest/login
  • /api/rest/myTickets

​

​

31 of 42

Report

​

​

​

32 of 42

Regression & Compatibility Testing

33 of 42

Regression Testing Report

34 of 42

Regression Testing Report

35 of 42

Compatibility (Cross-Browser) Testing Report

​

  • Firefox dan Chrome

36 of 42

Compatibility (Cross-Browser) Testing Report

​

  • Failed on Register Test

37 of 42

38 of 42

Reporting & Dashboard

39 of 42

Manual testing

​

  • Regression Testing Pass Rate

​

Pass

Fail

Success rate

16

5

76%

Pass

Fail

Success rate

11

1

90%

Automation testing

​

  • Regression Testing Pass Rate
  • API Testing Pass Rate
  • API Testing Pass Rate

Pass

Fail

Success rate

6

0

100%

Pass

Fail

Success rate

6

0

100%

Load Testing

​

  • Error Rate (50 users)

/login

/myTickets

43.14%

28.30%

40 of 42

Conclusion & Recommendation

41 of 42

Observation:

​

  • Automation testing pass rate 90%
  • Manual testing pass rate 76%
  • Compatibility 2 browser passed
  • Perbedaan Automation dan Manual Testing berada di scope testing, dimana manual testing lebih luas areanya (dari priority test case yg low sampai yg high) sehingga pass rate nya lebih rendah.
  • Load Test endpoint LOGIN users paling lambat, dengan rata-rata response time 11 detik dan error rate 43%, menandakan server kewalahan memproses autentikasi paralel.
  • Test yang di automate belum semuanya

​

​

Conclusion:

​

  • feature utama sudah bekerja baik secara fungsional
  • feature lain, masih banyak bug
  • sistem belum bisa menangani beban tinggi (contoh: autentikasi paralel)
  • sistem masih belum layak rilis untuk dipakai user

​

​

42 of 42

Terima

Kasih.