Benutzer:Embedded23/ContinoProva Englisch
| Embedded23/ContinoProva Englisch |
|---|
ContinoProva is a software tool for automated testing of embedded software. It acts as a framework and integrates various hardware and software tools for automated testing.
Etymology
The name ContinoProva is derived from the spanish word continuo (continuous) and the italian word provare (to test).
Fields of application
ContinoProva can be applied in several test stages, e.g., integration testing, system testing, as well as in tests during development and tests in real environments.[1]
It is also often used to perform regression testing due to its repetitive character and the frequency of these repetitions.[2]
Main fields of application of ContinoProva are the automotive industry and medical technology, as well as in railroad and automation technology.[3]
Architecture
ContinoProva is based on a client-server model. External tools are connected to the server via open interfaces (APIs). In the embedded systems development environment, these are, for example, relay boxes for controlling digital inputs of the test object, oscilloscopes for signal measurement, bus tools for setting and reading bus messages, and debuggers. The client requests individual services from the server during the test run according to the defined test specifications. The server forwards the client's requests to the test tools and, conversely, the tools' feedback to the client. This architecture abstracts from the user and programming interfaces of individual tools and provides a unified front end for test specification and control of tools.[4]
Usage in the test process according to ISTQB
Test specification
Tests are specified sequentially in the editor of ContinoProva via a graphical user interface (GUI). They are hierarchically structured in test groups, test sequences, test steps and test tasks. Connected tools can be addressed within a test specification. This sequential test sequence also enables other test specification types, e.g., statecharts, to be connected.[5]
Test execution
Automatic execution of tests can be performed in different modes. For example, conditions for the test sequence, as well as interrupts and loops can be defined. Recurring test elements (test stages, test sequences or test groups) may be defined as library modules and can be used in different test specifications. An integrated test debugger enables the processing of individual test stages. Test specifications can be tested repeatedly by means of batch processing.
Test evaluation
ContinoProva's generated report provides the user with configurable test reports in terms of content and form. The test report can contain the test specification, results of the comparison between expected and actual output values of the test object, information about the test environment as well as organizational data, e.g. name of the tester, time of the test and so forth.
See also
Weblinks
- ContinoProva Webseite
- ContinoProva YouTube-Kanal
- Eintrag auf www.testtoolreview.de
- Eintrag auf www.softguide.de
Further reading
- Andreas Spillner, Tilo Linz: Basiswissen Softwaretest. dpunkt Verlag, Heidelberg 2012. ISBN 978-3-86490-024-2.
References
- ↑ S. Sadeghipour: Testautomatisierung in einer heterogenen Toolumgebung, Embedded Testing 2017, München 2017, S. 10.
- ↑ Meike Lim, Frank Deus: Automatisierte Sicherheit. In: MEDengineering, 3–4/2014, S. 40, Kulmbach 2014.
- ↑ https://itpower.de/de/unternehmen/ueber-uns/ abgerufen am 25. Oktober 2018
- ↑ S. Sadeghipour: Testautomatisierung in einer heterogenen Toolumgebung, Embedded Testing 2017, München 2017, S. 3.
- ↑ S. Sadeghipour: Gleitender Übergang vom manuellen zum automatisierten Test eingebetteter Software, Fachgruppentreffen TAV 2017, Langen 2017, S3.
