The Importance of Testing in the Early Stages of Smart Contract Development Life Cycle

2020 ◽  
Author(s):  
N. Sánchez-Gómez ◽  
L. Morales-Trujillo ◽  
J. J. Gutiérrez ◽  
J. Torres-Valderrama
Keyword(s):  
Business Processes ◽  
Process Models ◽  
Test Case ◽  
Case Definitions ◽  
Smart Contract ◽  
Development Life Cycle ◽  
Early Testing ◽  
Modelling Techniques ◽  
Testing Techniques ◽  
The Cost

The use of smart contract augurs a world without intermediaries because the code and the agreements contained therein exist across a distributed, decentralized blockchain network. In software engineering, this collaboration is usually represented by using business process models and smart contracts can be used to implement business collaborations in general and inter-organizational business processes. The validation of this contract and the assurance of its quality are critical for its right application. Early testing in smart contract definition is the fact of this paper. The paper discusses the possibility to use transformation protocols to obtain derived artefacts like test case definitions and smart contract code scaffolds. Generation of derived artefacts significantly reduces the number of defects before deploying the smart contract code in the blockchain network. Transformations protocols are created using model-based software development and modelling techniques. This approach allows to simplify and improve the management and execution of collaborative business processes. This would allow, in addition, the application of systematic mechanisms to evaluate and validate the smart contract and, particularly, the application of early testing techniques which would help to reduce the number of defects and, ultimately, the cost of the final review.

Survey on Testing of BPEL Processes

2014 ◽  
Vol 13 (7) ◽  
pp. 4633-4637
Author(s):  
Gurpreet Kaur ◽  
Mrs. Gaganpreet Kaur
Keyword(s):  
Life Cycle ◽  
Software Testing ◽  
Test Case Generation ◽  
Test Case ◽  
Test Cases ◽  
Development Life Cycle ◽  
Testing Techniques ◽  
Critical Task ◽  
The Cost ◽  
Bpel Processes

Software testing is very important phase in any development Life Cycle. The test Case generation is critical task in any type of testing. The automation of test case generation is necessary to reduce cost and effort incurred in the testing of large software. Testing of the BPEL processes is new area of research and the automation of the test cases is necessary in order to find bugs in the processes and reduce the cost of the  testing business  processes .This paper focuses on the survey of the testing techniques used to test the BPEL processes.

Test Case Prioritization Technique Based on Error Probability and Severity of UML Models

2018 ◽  
Vol 28 (06) ◽  
pp. 831-844 ◽  
Author(s):  
Tianning Zhang ◽  
Xingqi Wang ◽  
Dan Wei ◽  
Jinglong Fang
Keyword(s):  
Flight Control ◽  
Error Probability ◽  
Unified Modeling Language ◽  
Test Case ◽  
Test Cases ◽  
Test Case Prioritization ◽  
Unified Modeling ◽  
Code Coverage ◽  
Development Life Cycle ◽  
The Cost

Test case prioritization is one of the most useful activities in testing. Most existing test case prioritization techniques are based on code coverage, which requires access to source code. However, code-based testing comes late in the software development life cycle, when errors are detected, the cost of testing is very high. Therefore, in this paper, we provide a test case prioritization technique based on Unified Modeling Language (UML) model, built before coding, to detect errors as earlier as possible and reduce the cost of modification. The technique consists of the following main parts: (1) using C&K metrics to estimate the error probability of class; (2) using dependences, obtained from the model slicing, to estimate error severity; (3) generating test case priority from error probability and severity, then prioritizing the test case. With our technique, test engineers need the UML model only and the test cases can be prioritized automatically. To evaluate our technique, we applied our technique to unmanned aerial vehicles (UAV) flight control system and performed test case prioritization. The results show that the error can be detected effectively and stability can be increased significantly as compared to the current code-based techniques.

scholarly journals HTTCS: Hybridization Technique for Test Case Selection

2018 ◽  
Vol 16 (2) ◽  
pp. 95-105
Author(s):  
Adtha LAWANNA
Keyword(s):  
Problem Solving ◽  
Software Maintenance ◽  
Test Case ◽  
Hybridization Technique ◽  
Test Cases ◽  
Test Case Selection ◽  
Whole Process ◽  
Case Selection ◽  
Development Life Cycle ◽  
The Cost

One problem found within the process of software maintenance is that the size of the selected test cases is large. This causes the ability of the whole process of software-development life cycle to drop. Particularly, it may be time consuming and cause delays, and the cost may be expensive. The selection of test cases for software maintenance depends more on the criticality of fixing bugs than the criticality of avoiding programming errors. Therefore, selection methods are proposed, such as test-all, random, and regression selection. This includes Technique for Test Case Selection (TTCS) and the improvement of Test Case Selection (TCS). These techniques can provide better results, in particular, giving smaller sizes, reduction rates, and % problem-solving than traditional techniques. However, this paper proposes a new model, which is a combination of using the process of determining an appropriate number of selected test cases regarding TTCS, and TCS with testing-based selection, named the Hybridization Technique for Test Case Selection (HTTCS). Obviously, HTTCS can reduce the size of the selected test cases by about 96.86 - 98.83 %, which is better than TTCS and TCS, by about 0.29 - 16.51 %. Additionally, using HTTCS can increase the % problem-solving by up to 99.98 %, is which higher than others about at most 0.66 %.

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

2018 ◽  
Vol 5 (1) ◽  
pp. 112-118
Author(s):  
Agus Pamuji
Keyword(s):  
Control Flow ◽  
Structural Testing ◽  
Test Case ◽  
Test Cases ◽  
Development Life Cycle ◽  
Testing Data ◽  
Result Show ◽  
Long Time ◽  
Data Flow Testing ◽  
Testing Techniques

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

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

2018 ◽  
Vol 5 (1) ◽  
pp. 112-118
Author(s):  
Agus Pamuji
Keyword(s):  
Control Flow ◽  
Structural Testing ◽  
Test Case ◽  
Test Cases ◽  
Development Life Cycle ◽  
Testing Data ◽  
Result Show ◽  
Long Time ◽  
Data Flow Testing ◽  
Testing Techniques

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

Keynote

2021 ◽  
Vol 48 (4) ◽  
pp. 3-3
Author(s):  
Ingo Weber
Keyword(s):  
Cost Estimation ◽  
Estimation Method ◽  
Main Topic ◽  
System Throughput ◽  
Distributed Ledger ◽  
Smart Contract ◽  
Distributed Ledger Technology ◽  
Wide Range ◽  
The Cost ◽  
Application Developers

Blockchain is a novel distributed ledger technology. Through its features and smart contract capabilities, a wide range of application areas opened up for blockchain-based innovation [5]. In order to analyse how concrete blockchain systems as well as blockchain applications are used, data must be extracted from these systems. Due to various complexities inherent in blockchain, the question how to interpret such data is non-trivial. Such interpretation should often be shared among parties, e.g., if they collaborate via a blockchain. To this end, we devised an approach codify the interpretation of blockchain data, to extract data from blockchains accordingly, and to output it in suitable formats [1, 2]. This work will be the main topic of the keynote. In addition, application developers and users of blockchain applications may want to estimate the cost of using or operating a blockchain application. In the keynote, I will also discuss our cost estimation method [3, 4]. This method was designed for the Ethereum blockchain platform, where cost also relates to transaction complexity, and therefore also to system throughput.

scholarly journals Automated Search-Based Robustness Testing for Autonomous Vehicle Software

2016 ◽  
Vol 2016 ◽  
pp. 1-15 ◽  
Author(s):  
Kevin M. Betts ◽  
Mikel D. Petty
Keyword(s):  
Monte Carlo ◽  
Performance Metrics ◽  
Initial Conditions ◽  
Autonomous Vehicle ◽  
Vehicle Control ◽  
Test Case ◽  
Test Cases ◽  
Control Software ◽  
Robustness Testing ◽  
Testing Techniques

Autonomous systems must successfully operate in complex time-varying spatial environments even when dealing with system faults that may occur during a mission. Consequently, evaluating the robustness, or ability to operate correctly under unexpected conditions, of autonomous vehicle control software is an increasingly important issue in software testing. New methods to automatically generate test cases for robustness testing of autonomous vehicle control software in closed-loop simulation are needed. Search-based testing techniques were used to automatically generate test cases, consisting of initial conditions and fault sequences, intended to challenge the control software more than test cases generated using current methods. Two different search-based testing methods, genetic algorithms and surrogate-based optimization, were used to generate test cases for a simulated unmanned aerial vehicle attempting to fly through an entryway. The effectiveness of the search-based methods in generating challenging test cases was compared to both a truth reference (full combinatorial testing) and the method most commonly used today (Monte Carlo testing). The search-based testing techniques demonstrated better performance than Monte Carlo testing for both of the test case generation performance metrics: (1) finding the single most challenging test case and (2) finding the set of fifty test cases with the highest mean degree of challenge.

Pengembangan SIA Terintegrasi: Pengaturan Pembelian Kredit di PT Toyonaga Indonesia

2019 ◽  
Vol 4 (1) ◽  
pp. 142-148
Author(s):  
Dealin Mahaputri Leonika
Keyword(s):  
Qualitative Research ◽  
Internal Control ◽  
Business Processes ◽  
System Development ◽  
Application System ◽  
Development Life Cycle ◽  
Descriptive Approach ◽  
System Information ◽  
Main Support ◽  
Developing System

Abstract-- PT Toyonaga Indonesia is a manufacturing company engaged in the automotive field, the importance of purchasing activities as the main support in the process production and as revenue company , it is very necessary for  system that is mutually integrated computerized between one part and another. PT Toyonaga Indonesia has no system that can integrate between parts to facilitate internal control of the company. This study using method a qualitative research with a descriptive approach, which developing system design using a system development, system structured cycle due to SDLC is a recognized method and is used a lot of system development, steps structured and practical, tools from SDLC using more diagrams so easy to understand, the stages are related to each other. The results show that the system has been running well in PT Toyonaga Indonesia, but the system has not run effectively and efficiently so it is designed with an application system called Entrepreneurial Purchasing System to facilitate the company's business processes, especially in the field of credit purchases.   Keywords-- System Information Accounting In Purchase Credit   Abstrak--PT Toyonaga Indonesia adalah perusahaan manufaktur yang bergerak dibidang otomotif, karena begitu pentingnya kegiatan pembelian sebagai penunjang utama dalam proses produksi dan perolehan profit perusahaan maka sangat dibutuhkannya sistem yang saling terintegrasi secara komputerisasi antara satu bagian dengan bagian lain. PT Toyonaga Indonesia belum terdapat sistem yang dapat berintegrasi antar bagian untuk memudahkan pengendalian internal perusahaan. Penelitian ini menggunakan metode penelitian kualitatif dengan pendekatan deskriptif yaitu dengan mengembangkan perancangan sistem dengan menggunakan sistem tersturktur System Development Life Cycle karena SDLC merupakan metode yang diakui dan digunakan banyak pengembangan sistem, alur tahapannya terstruktur dan praktis, tools alat-alat dari SDLC menggunakan diagram yang lebih mudah dimengerti, tahapannnya terkait satu sama lainnya. Hasil penelitian menunjukan bahwa sistem yang berjalan pada PT Toyonaga Indonesia sudah berjalan dengan baik, namun sistem belum berjalan secara efektif dan efisien maka dirancang dengan sistem aplikasi dengan nama Purchasing Entris System agar memudahkan proses bisnis perusahaan khususnya dalam bidang pembelian kredit.   Kata Kunci--Sistem Informasi Akuntansi Pembelian Kredit    

CRITICAL ANALYSIS OF APPROACHES TO ASSESSING THE IMPACT OF BUSINESS PROCESSES ON THE FINANCIAL PERFORMANCE OF AN ORGANIZATION

2021 ◽  
Vol 4 (4) ◽  
pp. 201-205
Author(s):  
A. L. GENDON ◽  
◽  
G. F. GOLUBEVA ◽  
Keyword(s):  
Financial Performance ◽  
Critical Analysis ◽  
Business Processes ◽  
International Standards ◽  
Financial Indicators ◽  
Life Activity ◽  
Cost Of Production ◽  
The Cost ◽  
The Impact

The article reveals a system of financial indicators that characterize business processes, accounting for income and expenses according to Russian and international standards. The ways of increasing the efficiency of the company's life activity, in particular, the ways of reducing the cost of production, are considered.

Sign in / Sign up

Export Citation Format

Share Document