Expecco

from Wikipedia, the free encyclopedia
expecco
Basic data

developer eXept Software AG
Current  version 2019-2
(December 2019)
operating system Microsoft Windows , Linux
category Test automation
License Commercial, Trial version available, Free for research and teaching
German speaking Yes
www.exept.de

Expecco ( spelling : expecco) is a tool for the graphic development, execution and automation of test cases in the field of software and hardware tests. Test cases are graphically modeled as activity diagrams and at the push of a button (i.e. without the intermediate step of a generator) converted into executable code using dynamic just-in-time compilation and executed. The explorative test creation is supported by debug functions (single step, breakpoints, trace of functions and data flows). Areas of application are primarily integration and acceptance tests as well as regression tests of complex systems from the automotive, aerospace, telecommunications, automation and control as well as logistics, banking and financial software sectors.

methodology

Expecco is a black box test system. The System Under Test (SUT) is simulated by the test system via interfaces (incentives), and its correct behavior is then verified directly or via measuring and testing devices. Both incentives and verification are performed by the test system. Test cases are primarily modeled as activity diagrams with functional action modules. For this purpose, action modules are hierarchically combined to form more complex actions. The transfer of parameters, input values ​​and results takes place according to the data flow model via configurable queues (see Colored Petrinet and Flow Based Programming ). Elementary action modules are placed from existing libraries using drag and drop . However, it is also possible for the user or third-party providers to create them themselves in a JavaScript- like script language. The scripting language is part of the tool and therefore cross-platform. Test suites can be developed and executed on Windows, Linux and Unix based systems without modification. By parameterizing and virtualizing blocks, partial sequences can be reused in several test cases.

Test sequences can be graphically modeled and automated without programming knowledge. For communication with the System Under Test , however, elementary modules are typically required which implement the interface to existing functions as a function call in a DLL , Java or .NET class or the call of external programs or services ( SOAP , XML-RPC , REST ). This can be seen as a disadvantage, since it requires a certain amount of programming experience.

By combining graphic modeling with dynamic translation, the attempt is made to avoid the problems of classic model-based development (long turn around times, difficult troubleshooting in the model).

Main features:

  • Modeling test cases as an activity diagram
  • Short turn-around times thanks to dynamic just-in-time compilation
  • Support of the test development process through extended debug functions
  • Platform independent
  • Self-documenting, (model represents execution specification)

Interfaces

Communication with the SUT takes place via interface modules, which are combined in domain-specific libraries. These support u. a .:

Import of test descriptions

Activity diagrams can be partially or fully imported in various formats: XMI , Enterprise Architect , BPEL , MindMaps, Word and Excel test case descriptions.

Integration into the infrastructure

Expecco itself can be started by other tools as part of company-wide quality management and, if necessary, can also be controlled remotely. Expecco can be combined with Jenkins / Hudson , Polarion, HP Quality Center and other tools and generate reports in compatible formats (JUnit-XML, PDF , text etc.). Tests can also be started and controlled by any other program via SOAP , XML-RPC or Telnet .

commitment

The software is used by various companies around the world, including Airbus , Brose , Alcatel-Lucent , Swisscom , UBS , Deutsche Telekom , T-Systems and Visteon .

Web links

Individual evidence

  1. ↑ Paul Baker, Zhen Ru Dai, Jens Grabowski; Haugen, Oystein, Ina Schieferdecker, Clay Williams: Model Driven Testing - Using the UML Testing Profile. Springer-Verlag, Berlin / Heidelberg 2008, ISBN 978-3-540-72562-6 .
  2. ↑ agilemodeling.com