Claim Missing Document
Check
Articles

Found 3 Documents
Search

Comparing Karate Framework with Others for Automated Regression Testing: A Case Study of PT Fliptech Lentera Inspirasi Pertiwi Dayanti, Afina Putri; Tony, Tony
ULTIMATICS Vol 16 No 1 (2024): Ultimatics : Jurnal Teknik Informatika
Publisher : Faculty of Engineering and Informatics, Universitas Multimedia Nusantara

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.31937/ti.v16i1.3397

Abstract

In the rapidly evolving digital era, applications, and software systems increasingly rely on Application Programming Interfaces (APIs) to enable interaction, integration, and functionality extension. However, manual testing of APIs is often inefficient and challenging to reuse when changes occur. To address this, automation testing has become a more effective choice, where test scripts can verify and execute tests repeatedly, easily adapting to API changes. Essentially, automation testing plays a vital role in software maintenance, particularly in regression testing, which tests modified or upgraded software versions to ensure that their core functions remain unchanged and unaffected. One approach to automation testing is employing the Software Testing Life Cycle (STLC), which follows a systematic series of stages conducted by the testing team to ensure software product quality. This paper utilizes PT Fliptech Lentera Inspirasi Pertiwi’s public API to conduct testing on 25 scenarios from two modules. The objective is to utilize the Karate Framework to conduct these automated regression tests, resulting in an impressively short testing duration, averaging only 42.645 seconds, or approximately 1.706 seconds per scenario. A comparison with the Behave framework, using the same scenarios but with differences in steps, reveals that Behave achieves a duration of 18.762 seconds, or 0.750 seconds per scenario, making it 127.295% faster than Karate. However, in terms of the number of steps, Behave covers only 188, while Karate includes 543. This means that Behave requires 0.100 seconds per step, while Karate necessitates 0.079 seconds per occurrence. Karate provides more detailed results by 188.830% per step or 26.582% in terms of step duration. The primary goal is to enhance testing efficiency, expedite issue identification and resolution, provide a clearer testing process, and potentially improve overall software quality.
Dashboard Design to Monitor the Number of Students of the Faculty of Information Technology, Tarumanagara University Tony, Tony; Handhayani, Teny; Dayanti, Afina Putri
Sebatik Vol. 28 No. 2 (2024): December 2024
Publisher : STMIK Widya Cipta Dharma

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.46984/sebatik.v28i2.1942

Abstract

Students in a study program within the faculty are important stakeholders in higher education. The continuity and efficiency of teaching and learning activities depend significantly on the number of students in a study program. The Faculty of Information Technology at Tarumanagara University currently offers two study programs: Informatics Engineering and Information Systems. While Tarumanagara University already has a system for managing student data, it requires further development to remain competitive with other universities, particularly those offering information technology programs. The existing system provides only basic information, such as whether the number of students this year has increased or decreased compared to the previous year. However, it lacks the ability to deliver a comprehensive overview of student data. To address this limitation, a monitoring system is needed to provide more accurate and systematic information. This system will be visualized in the form of a dashboard, offering insights into trends such as the number of students, their school origins, gender distribution, and address/region of origin. The dashboard design is based on the waterfall model of the software development life cycle (SDLC) and is developed using Power BI Desktop.
Comparing Karate Framework with Others for Automated Regression Testing: A Case Study of PT Fliptech Lentera Inspirasi Pertiwi Dayanti, Afina Putri; Tony, Tony
ULTIMATICS Vol 16 No 1 (2024): Ultimatics : Jurnal Teknik Informatika
Publisher : Faculty of Engineering and Informatics, Universitas Multimedia Nusantara

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.31937/ti.v16i1.3397

Abstract

In the rapidly evolving digital era, applications, and software systems increasingly rely on Application Programming Interfaces (APIs) to enable interaction, integration, and functionality extension. However, manual testing of APIs is often inefficient and challenging to reuse when changes occur. To address this, automation testing has become a more effective choice, where test scripts can verify and execute tests repeatedly, easily adapting to API changes. Essentially, automation testing plays a vital role in software maintenance, particularly in regression testing, which tests modified or upgraded software versions to ensure that their core functions remain unchanged and unaffected. One approach to automation testing is employing the Software Testing Life Cycle (STLC), which follows a systematic series of stages conducted by the testing team to ensure software product quality. This paper utilizes PT Fliptech Lentera Inspirasi Pertiwi's public API to conduct testing on 25 scenarios from two modules. The objective is to utilize the Karate Framework to conduct these automated regression tests, resulting in an impressively short testing duration, averaging only 42.645 seconds, or approximately 1.706 seconds per scenario. A comparison with the Behave framework, using the same scenarios but with differences in steps, reveals that Behave achieves a duration of 18.762 seconds, or 0.750 seconds per scenario, making it 127.295% faster than Karate. However, in terms of the number of steps, Behave covers only 188, while Karate includes 543. This means that Behave requires 0.100 seconds per step, while Karate necessitates 0.079 seconds per occurrence. Karate provides more detailed results by 188.830% per step or 26.582% in terms of step duration. The primary goal is to enhance testing efficiency, expedite issue identification and resolution, provide a clearer testing process, and potentially improve overall software quality.