Advertisement

Structural Test Coverage Criteria for Integration Testing of LUSTRE/SCADE Programs

  • Virginia Papailiopoulou
  • Ajitha Rajan
  • Ioannis Parissis
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6959)

Abstract

Lustre is a formal synchronous declarative language widely used for modeling and specifying safety-critical applications in the fields of avionics, transportation, and energy production. In such applications, the testing activity to ensure correctness of the system plays a crucial role in the development process. To enable adequacy measurement of test cases over applications specified in Lustre (or SCADE), a hierarchy of structural coverage criteria for Lustre programs has been recently defined. A drawback with the current definition of the criteria is that they can only be applied for unit testing, i.e., to single modules without calls to other modules. The criteria experiences scalability issues when used over large systems with several modules and calls between modules. We propose an extension to the criteria definition to address this scalability issue. We formally define the extension by introducing an operator to abstract calls to other modules. This extension allows coverage metrics to be applied to industrial-sized software without an exponential blowup in the number of activation conditions. We conduct a preliminary evaluation of the extended criteria using an Alarm Management System.

Keywords

Activation Condition Operator Network Test Sequence Coverage Criterion Node Operator 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Benveniste, A., Caspi, P., Edwards, S.A., Halbwachs, N., Le Guernic, P., de Simone, R.: The synchronous languages 12 years later. Proceedings of the IEEE 91(1), 64–83 (2003)CrossRefGoogle Scholar
  2. 2.
    Chilenski, J.J., Miller, S.P.: Applicability of modified condition/decision coverage to software testing 9(5), 193–200 (1994)Google Scholar
  3. 3.
    DeMillo, R.A.: Test Adequacy and Program Mutation. In: International Conference on Software Engineering, pp. 355–356. Pittsburg, PA (1989)CrossRefGoogle Scholar
  4. 4.
    Halbwachs, N., Caspi, P., Raymond, P., Pilaud, D.: The synchronous data flow programming language lustre. Proceedings of the IEEE 79(9), 1305–1320 (1991)CrossRefGoogle Scholar
  5. 5.
    Halbwachs, N., Lagnier, F., Ratel, C.: Programming and verifying real-time systems by means of the synchronous data-flow language lustre. IEEE Trans. Software Eng. 18(9), 785–793 (1992)CrossRefzbMATHGoogle Scholar
  6. 6.
    Lakehal, A., Parissis, I.: Structural coverage criteria for lustre/scade programs. Softw. Test., Verif. Reliab. 19(2), 133–154 (2009)CrossRefGoogle Scholar
  7. 7.
    Marre, B., Arnould, A.: Test sequences generation from lustre descriptions: Gatel. In: IEEE International Conference on Automated Software Engineering, Grenoble, France, pp. 229–237 (October 2000)Google Scholar
  8. 8.
    Papailiopoulou, V., Madani, L., du Bousquet, L., Parissis, I.: Extending structural test coverage criteria for lustre programs with multi-clock operators. In: The 13th International Workshop on Formal Methods for Industrial Critical Systems (FMICS), L’Aquila, Italy (September 2008)Google Scholar
  9. 9.
    Raymond, P., Nicollin, X., Halbwachs, N., Weber, D.: Automatic testing of reactive systems. In: IEEE Real-Time Systems Symposium, pp. 200–209 (1998)Google Scholar
  10. 10.
    Woodward, M.R., Hedley, D., Hennell, M.A.: Experience with path analysis and testing of programs. IEEE Trans. Softw. Eng. 6(3), 278–286 (1980)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Virginia Papailiopoulou
    • 1
  • Ajitha Rajan
    • 2
  • Ioannis Parissis
    • 3
  1. 1.INRIA RocquencourtFrance
  2. 2.Université Joseph Fourier - Laboratoire d’Informatique de GrenobleFrance
  3. 3.Grenoble INP - Laboratoire de Conception et d’Intègration des SystèmesFrance

Personalised recommendations