References

  1. T. Arts & J. Hughes (2016): How Well are Your Requirements Tested?. In: 2016 IEEE International Conference on Software Testing, Verification and Validation, pp. 244–254, doi:10.1109/ICST.2016.23.
  2. T. Arts, J. Hughes, J. Johansson & U. Wiger (2006): Testing telecoms software with QuviQ QuickCheck. In: Proceedings of ERLANG'06. ACM, pp. 2–10, doi:10.1145/1159789.1159792.
  3. T. Arts, J. Hughes, U. Norell & H. Svensson (2015): Testing AUTOSAR software with QuickCheck. In: Eighth IEEE International Conference on Software Testing, Verification and Validation Workshops, pp. 1–4, doi:10.1109/ICSTW.2015.7107466.
  4. T. Arts & M.R. Mousavi (2015): Automatic Consequence Analysis of Automotive Standards (AUTO-CAAS). In: First International Workshop on Automotive Software Architectures (WASA 2015). ACM Press, pp. 35–38, doi:10.1145/2752489.2752495.
  5. AUTOSAR Consortium (2013): AUTomotive Open System ARchitecture, standard documents. https://autosar.org/.
  6. AUTOSAR Consortium (2014): Acceptance Test Specification of Communication on CAN bus – Release 1.0.0.
  7. F. Cesarini & S. Thompson (2009): Erlang Programming. O'Reilly.
  8. J. Hughes (2007): QuickCheck testing for fun and profit. In: Proceedings of PADL'07. Springer, pp. 1–32, doi:10.1007/978-3-540-69611-7_1.
  9. S. Kunze, W. Mostowski, M.R. Mousavi & M. Varshosaz (2016): Generation of Failure Models through Automata Learning. In: Second International Workshop on Automotive Software Architectures (WASA 2016). IEEE Society, pp. 22–25, doi:10.1109/WASA.2016.7.
  10. J. Svenningsson, H. Svensson, N. Smallbone, T. Arts, U. Norell & J. Hughes (2014): An Expressive Semantics of Mocking. In: Fundamental Approaches to Software Engineering, LNCS 8411. Springer, pp. 385–399, doi:10.1007/978-3-642-54804-8_27.
  11. J. Tretmans (2011): Model-Based Testing and Some Steps towards Test-Based Modelling. In: Formal Methods for Eternal Networked Software Systems, LNCS 6659. Springer, pp. 297–326, doi:10.1007/978-3-642-21455-4_9.

Comments and questions to: eptcs@eptcs.org
For website issues: webmaster@eptcs.org