CAST: Automating Software Tests for Embedded Systems

Wahler, Michael; Ferranti, Ettore; Steiger, Robin; Jain, Rahul; Nagy, Kristian

doi:10.1109/icst.2012.126

Cited by 15 publications

(4 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In paper [6], Computer-Aided Specification and Testing (CAST) approach is proposed to automate the process of testing embedded systems. The flaws of manual testing have motivated the authors to switch to automation.…”

Section: Related Workmentioning

confidence: 99%

Test Automation Framework for Embedded Linux Testing

Sahana¹,

Maanas²,

Raju³

2021

JUSST

View full text Add to dashboard Cite

Software testing is one of the most important steps before its official roll–out to the market. Testing of embedded software is a very complex, tedious, and time–consuming process. Manual execution of the test cases can pose a huge challenge to the test engineers in terms of the time consumed to execute and compile the results of hundreds of test cases. This paper presents a solution to automate the entire process of build and install of Board Support Package (BSP) using Jenkins, along with the automation of the testing process using Linaro Automation and Validation Architecture (LAVA). The proposed design is validated in a BSP testing environment to show the ease of testing using the framework mentioned in this paper.

show abstract

Section: Related Workmentioning

confidence: 99%

Test Automation Framework for Embedded Linux Testing

Sahana¹,

Maanas²,

Raju³

2021

JUSST

View full text Add to dashboard Cite

show abstract

“…Moreover, in most cases measurement of the execution time is performed in real working conditions, but not in some artificial, laboratory environment, completely different from the real one. Typically, dynamic methods are applied to measure the firmware execution time using a logical analyzer or an oscilloscope [11,12], hardware tracing [13,14], integration of an additional code into an embedded system being tested [15,16] or simulators of an embedded system [17]. Each of these approaches has their advantages and disadvantages.…”

Section: Relevant Workmentioning

confidence: 99%

A Method of Predicting the Maintenance Period of Embedded Systems for Preventing Breach of Their Time Requirements

Fedasyuk¹,

Marusenkova²,

Chopey³

2018

IJC

View full text Add to dashboard Cite

The work deals with a significant problem of ensuring that the execution time of a firmware running inside a microcontroller-based real-time embedded system never goes out of its expected range, no matter for how long the embedded system has been used. Once having been tested before the first usage, a newly created embedded system is gradually getting slower in its response, due to the fact that its hardware components get worn-out with aging. A possible solution is a replacement of the hardware components that most contribute to such a change in the response time of the embedded system. If such a replacement takes place too far in advance, long before hardware components actually start showing any decline in their response time, the above-mentioned solution is cost-ineffective and impractical, as it leads to a waste of equipment and efforts. We introduce a method for predicting the appropriate maintenance period of a real-time embedded system on the basis of the characteristics of its hardware components.

show abstract

“…Depending on their type, model and the time of being in use, i.e., when a peripheral device wears out, its characteristics make their operation slower in general and their behaviors become less determined. In order to evaluate the firmware's execution time, they use the following metrics: worst-case execution time (WCET) [3,4], best-case execution time (BCET) [5,6] and average-case execution time, (ACET) [7,8]. The latter resides within the interval [BCET -WCET] and depends on the distribution of the program execution time.…”

Section: Introductionmentioning

confidence: 99%

A Model for Estimating Firmware Execution Time Taking Into Account Peripheral Behavior

Fedasyuk¹,

Marusenkova²,

Chopey³

2018

IJISA

View full text Add to dashboard Cite

Abstract-The paper deals with the problem of estimating the execution time of firmware. Any firmware is bound to wait for a response from peripheral devices such as external memory chips, displays, analog-todigital converters, etc. The firmware's execution is frozen until the expected response is obtained. Thus, any firmware's execution time depends not only on the computational resources of the embedded system being inspected but also on peripheral devices each of which is able to perform a set of operations during some random time period residing, however, within a known interval. The paper introduces a model of a computer application for evaluation of microcontroller-based embedded systems' firmware's execution time that takes into consideration the type of the microcontroller, the total duration of all the assembler-like instructions for a specific microcontroller, all the occasions of waiting for a response from hardware components, and the possible time periods for all the responses being waited for. Besides, we proposed the architecture of the computer application that assumes a reusable database retaining data on microcontrollers' instructions.

show abstract

CAST: Automating Software Tests for Embedded Systems

Cited by 15 publications

References 9 publications

Test Automation Framework for Embedded Linux Testing

Test Automation Framework for Embedded Linux Testing

A Method of Predicting the Maintenance Period of Embedded Systems for Preventing Breach of Their Time Requirements

A Model for Estimating Firmware Execution Time Taking Into Account Peripheral Behavior

Contact Info

Product

Resources

About