• Proceedings of the KSRS Conference
• /
• 2008.10a
• /
• pp.84-87
• /
• 2008

ATTOL is a software unit testing tool produced by the ATTOL Testware SA in France. It automates the entire software unit testing process: test plan template and test program generation, test program execution, test result analysis and test report generation. ATTOL is suited for the development of embedded software as it allows programmers to operate in native and cross development environments. Particularly, it is used for the development of the flight software which is embedded in the Communication Ocean Meteorological Satellite (COMS). As the flight software is mission-critical, it requires the strict software quality and high testing constraints. The flight software of COMS is verified by ATTOL in native and cross platforms. In 2002, ATTOL was taken over by the IDM Rational Software and has been supplied with the name of Test RealTime (TestRT). The test process of TestRT becomes different from that of ATTOL as TestRT provides the new functionalities that were absent from ATTOL. TestRT provides the new features in the test script language, as well. In this paper, we compare the test process of ATTOL to TestRT With an example of COMS and explain what has been changed in the test script language.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.8
• /
• pp.2974-2992
• /
• 2021

Crowd-based outsourcing is an emerging trend in testing, which integrates advantages of crowd-based outsourcing in software testing. Open call format is used to accomplish various network tasks involving different types of testing levels and techniques at various places by software testers. Crowd-sourced software testing can lead to an improper testing process as if it does not allocate the right task to the right crowd with required skills and not choose the right crowd; it can lead to huge results, which become time-consuming and challenging crowd-source manager for the identification of improper one. The primary purpose of this research is to make crowd-based outsourced software testing more effective and reliable by relating association between the software tester, personality characteristic, and different levels of software testing, i.e., unit, integration, and system, in order to find appropriate personality characteristic for required testing level. This research has shown an observed experiment to determine which software testing level suits which personality characteristic tester in a crowd-based software testing environment. A total of 1000 software testers from different software houses and firms in Pakistan were registered to perform tasks at different software testing levels. The Myers-Briggs Type Indicator (MBTI) test is used to identify each tester's personality characteristic involved in this research study.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.12
• /
• pp.1-10
• /
• 2011

As requirements of embedded system get complicated, the tool for analyzing the reliability of embedded software is being needed. A probabilistic modeling is used as the way of analyzing the reliability of a software and to apply it to embedded software controlling multiple devices. So, it is necessary to specialize that to embedded software. Also, existing reliability analyzers should measure the transition probability of each condition in different ways and doesn't consider reusing the model once used. In this paper, we suggest a reliability analyzer for embedded software using embedded software Markov chin model and a unit testing tool. Embedded software Markov chain model is model specializing Markov chain model which is used for analyzing reliability to an embedded software. And a unit testing tool has host-target structure which is appropriate to development environment of embedded software. This tool can analyze the reliability more easily than existing tool by automatically measuring the transition probability between units for analyzing reliability from the result of unit testing. It can also directly apply the test result updated by unit testing tool by representing software model as a XML oriented document and has the advantage that many developers can access easily using the web oriented interface and SVN store. In this paper, we show reliability analyzing of a example by so doing show usefulness of reliability analyzer.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.205-218
• /
• 2011

Unit testing which is the first task to perform software testing has a major impact on reducing s/w development cost and improving s/w quality. In order to make unit testing become the formal procedure rather than ad-hoc tasks performed by developer, the language-neutral measures are necessary in the programming which is able to specify the test cases. This paper presents a test assertion language for the language-neutral specification of the test cases. The suggested language is based on the ISO/IEC 24709-1, but it supports object oriented features and can describe test cases for unit testing. The test cases that are specified by the language can be used for generating test oracle source codes by test oracle generation tools.

• Journal of Korean Society for Quality Management
• /
• v.29 no.4
• /
• pp.92-102
• /
• 2001

Software testing during development and operation should exercise to obtain the desired software quality and leave failure data set. So far, many software reliability models are classified and can be used to measure a software reliability only based on its failure history But, in practice, developers or testers of software systems must decide which existing software reliability model can be fitted. In this paper, we will show that an appropriate reliability model can be selected by considering relations between characteristics of each testing environment and models' assumptions. Several methods of software testing are presented and discussed. Also, unit test, integrated test, function test and system test that are sequentially exercised during development will be introduced.

• KIPS Transactions on Software and Data Engineering
• /
• v.4 no.9
• /
• pp.419-424
• /
• 2015

As Internet of Things (IoT) is recently serviced in several fields, the reliability and safety issues for IoT embedded systems are emerged. During the development of embedded systems, it is not easy to build the virtual execution environment and to test the developing version. Therefore, it is difficult to ensure its reliability due to lack of unit testing. In this paper, we propose a log-based unit testing framework for embedded software, which performs on real target board by extracting information of function execution. And, according to execution paths, duplicated logs are eliminated to keep a minimal log size. As a result, during system testing, testers can efficiently decide whether the executed paths of each function are correctly performed or not.

• IE interfaces
• /
• v.25 no.4
• /
• pp.416-421
• /
• 2012

One of the activities to improve software quality in ISO 26262 is to apply the design principles for software unit design and implementation mentioned in ISO 26262-6, including the evaluation activity. Before evaluation activity, the tool is compared and selected for evaluation. Because the results of the tool a company selected might have an effect on product quality. In this paper, we suggest the method to compare industrial static analysis tools with some of "MISRA C : 2004 Exemplar Suite" and all lessons learned from comparing tools are described. The result on comparison shows that we just couldn't rely on a result of Static Analysis Tool and need to have another appropriate processes and guidelines to evaluate a software.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.11
• /
• pp.1061-1065
• /
• 2010

AUTOSAR, a standard software platform for automotive, has been developed to manage software complexity and improve software reuseability. However Automated and standardized testing is needed to improve reliability and reduce time and effort on testing. Fundamental functionality of AUTOSAR RTE and basic software modules is guaranteed by using an AUTOSAR tool, but application software components have to be tested thoroughly. In this paper, we suggest a test system for the AUTOSAR software component using TTCN-3, a standardized testing language. Test execution system and test cases for the software component are generated automatically from AUTOSAR XML containing software design information. With the proposed testing techniques we can reduce time and effort to build the testing system.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.5 no.1
• /
• pp.29-38
• /
• 2010

It is highly requested that the more complicated embedded software is used for high performance and multiple functions of the systems. This is inevitably increasing the errors. Therefore the embedded software testing is getting important recently. There are not general testing methods which are able to be applied for any embedded systems, but via this research, we introduce a testing method which is based on TTCN-3, a testing standard, for embedded systems. A testing environment for network-based embedded software is implemented with considering the features of TTCN-3 testing which is based on message exchange. The testing environment has two additional parts with TTCN-3 test system, the network analyzer to access the network-based systems and the communication interface which is suggested for embedded systems in previous work, and we have implemented the whole testing environment with interacting these two parts. In addition to the normal testing domain, called single node testing as a unit testing of V-model, we suggest another concept to test multiple nodes in network. It could be achieved by adding keywords such as supervisor and object which are describing the feature of TTCN-3 testing component and generating the TTCN-3 Executable code which contains new keywords. The testing has done for embedded software which is based on CAN network and the demonstration of the testing environment has been shown in this paper.

• Journal of Applied Reliability
• /
• v.16 no.3
• /
• pp.216-223
• /
• 2016

Purpose: This paper suggests the procedure to enhance the reliability of the software of the medical device that is to cure, treat, diagnose, and prevent a disease or an abnormal health conditions. Methods: After test requirements are classified by the software requirements specification for safety and backgrounds, reliability assessment methods are suggested. Results: Verification and validation for function and safety can be performed whether the medical device software are implemented as intended. Conclusion: Procedure on the static analysis, unit test, integration test, and system test are provided for the medical device software.