You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Automation of the Creation and Execution of System Level Hardware-in-Loop Tests through Model-Based Testing

Fulltext:


Publication Type:

Conference/Workshop Paper

Venue:

The 13th Workshop on Automating Test Case Design, Selection and Evaluation


Abstract

In this paper, we apply model-based testing (MBT) to automate the creation of hardware-in-loop (HIL) test cases. In order to select MBT tools, different tools’ properties were compared to each other through a literature study, with the result of selecting GraphWalker and MoMuT tools to be used in an industrial case study. The results show that the generated test cases perform similarly to their manual counterparts regarding how the test cases achieved full require- ments coverage. When comparing the effort needed for applying the methods, a comparable effort is required for creating the first iteration, while with every subsequent update, MBT will require less effort compared to the manual process. Both methods achieve 100% requirements coverage, and since manual tests are created and executed by humans, some requirements are favoured over others due to company demands, while MBT tests are generated randomly. In addition, a comparison between the used tools showcased the differences in the models’ design and their test case generation. The comparison showed that GraphWalker has a more straightforward design method and is better suited for smaller systems, while Mo- MuT can handle more complex systems but has a more involved design method.

Bibtex

@inproceedings{Karlsson6555,
author = {Viktor Aronsson Karlsson and Ahmed Almasri and Eduard Paul Enoiu and Wasif Afzal and Peter Charbachi},
title = {Automation of the Creation and Execution of System Level Hardware-in-Loop Tests through Model-Based Testing},
month = {November},
year = {2022},
booktitle = {The 13th Workshop on Automating Test Case Design, Selection and Evaluation},
url = {http://www.es.mdh.se/publications/6555-}
}