Test Case Generation for Data Flow Testing using Cuckoo Search Algorithm

Software testing consumes the major portion of the total efforts required for software development. This activity is very time consuming and labor intensive. It is very hard to do testing in optimal manner. In this paper a new approach is proposed, which uses the nature inspired stochastic algorithm called Cuckoo Search Algorithm (CSA) for the automatic generation of test data for data flow testing. This approach considers all def-use as test adequacy criteria. For assistance to CSA in the state space a new fitness function is also proposed by using the concept of dominator tree and branch distance in a CFG. To validate the proposed approach experiments are carried out on 10 benchmarked programs and findings are contrasted with earlier work done in this domain. Further in order to prove that proposed approach performs better than the above mentioned approaches a statistical difference test (T-test) is also performed.

Automation of Data Flow Class Testing Using hybrid Evolutionary Algorithms

Background: Software testing is a time consuming and costly process. Recent advances in complexity of software have gained attention among researchers towards the automation of generation of test data. Objective: This paper focuses on the structural testing of object oriented paradigm based software and proposes a hybrid approach to automate the class testing applying heuristic algorithms. Method:The proposed algorithm performs data flow testing of classes applying all def-uses adequacy criteria by automatically generating test cases. A nested 2-step methodology is applied using meta-heuristic genetic algorithm and its two variant (GA-variant1 and Ga-variant2) to produce optimized method sequences. Results: An experiment is performed applying proposed algorithm on six test classes. The results suggest that proposed approach with GA-variant1 is better than other techniques in terms of Average d-u coverage and Average iterations.

Strategi Perbaikan Uji Coba Struktural Perangkat Lunak Pada Metode White-Box

Abstrak Uji coba perangkat lunak merupakan aktifitas yang sangat menentukan sebelum diterima oleh pengguna akhir. Pada siklus pengembangan perangkat lunak, aktiftas uji coba menghabiskan 50% biaya, usaha, dan waktu. Hal ini terutama pada teknik pengujian dengan menggunakan metode white-box yang memerlukan waktu yang lama. Dalam penelitian ini, diusulkan sebuah strategi untuk memperbaiki uji coba struktural menggunakan 4 tahap uji coba yaitu uji alur kontrol, uji alur data, uji coba berbasis slice, uji coba mutasi melalui penerapan parameter metrik uji. Adapun metrik uji antara lain perancangan jumlah kasus uji, jumlah kasus uji dieksekusi, jumlah kasus uji lolos, jumlah kasus uji gagal, waktu ekseskusi kasus uji, dan waktu yang digunakan selama proses pengembangan. Metode ini untuk mengurangi rawan kesalahan dan mempercepat proses uji coba. Hasil akhir menunjukan bahwa dengan strategi uji coba yang diterapkan dapat menurunkan tingkat dan rawan jumlah kesalahan walapun pada awalnya mengalami peningkatan pada tahap 1 dan 2. Kata Kunci: uji coba, metrik uji, strategi, struktural, white-box Abstract Software testing is a crucial activity that have the goal to determine before it are accepted by end-users. In the software development life cycle, testing activity has spent about 50% on cost, effort, and the time. This is especially on the testing techniques when the using white-box method that have takes a long time. In this study, a strategy was proposed to improve the structural testing through four phases, i.e, control flow testing, data flow testing, slice based testing, and the mutation through the implementation of testing metrics parameter. The testing metric include designing the number of test case, a number of test cases executed, a number of test cases passed, a number of test cases failed, a test case execution time, and the time spent during the development process. This method are reduced the error prone and to increas during testing process. As a result show that with the experimental strategy was applied could decrease the level and prone to the number of errors even though initially increased on the 1 and 2 phases. Keywords: testing, testing metrics, strategy, structural, white-box

Strategi Perbaikan Uji Coba Struktural Perangkat Lunak Pada Metode White-Box

Abstrak Uji coba perangkat lunak merupakan aktifitas yang sangat menentukan sebelum diterima oleh pengguna akhir. Pada siklus pengembangan perangkat lunak, aktiftas uji coba menghabiskan 50% biaya, usaha, dan waktu. Hal ini terutama pada teknik pengujian dengan menggunakan metode white-box yang memerlukan waktu yang lama. Dalam penelitian ini, diusulkan sebuah strategi untuk memperbaiki uji coba struktural menggunakan 4 tahap uji coba yaitu uji alur kontrol, uji alur data, uji coba berbasis slice, uji coba mutasi melalui penerapan parameter metrik uji. Adapun metrik uji antara lain perancangan jumlah kasus uji, jumlah kasus uji dieksekusi, jumlah kasus uji lolos, jumlah kasus uji gagal, waktu ekseskusi kasus uji, dan waktu yang digunakan selama proses pengembangan. Metode ini untuk mengurangi rawan kesalahan dan mempercepat proses uji coba. Hasil akhir menunjukan bahwa dengan strategi uji coba yang diterapkan dapat menurunkan tingkat dan rawan jumlah kesalahan walapun pada awalnya mengalami peningkatan pada tahap 1 dan 2. Kata Kunci: uji coba, metrik uji, strategi, struktural, white-box Abstract Software testing is a crucial activity that have the goal to determine before it are accepted by end-users. In the software development life cycle, testing activity has spent about 50% on cost, effort, and the time. This is especially on the testing techniques when the using white-box method that have takes a long time. In this study, a strategy was proposed to improve the structural testing through four phases, i.e, control flow testing, data flow testing, slice based testing, and the mutation through the implementation of testing metrics parameter. The testing metric include designing the number of test case, a number of test cases executed, a number of test cases passed, a number of test cases failed, a test case execution time, and the time spent during the development process. This method are reduced the error prone and to increas during testing process. As a result show that with the experimental strategy was applied could decrease the level and prone to the number of errors even though initially increased on the 1 and 2 phases. Keywords: testing, testing metrics, strategy, structural, white-box