Expecco Overview/en - Versionsgeschichte

Cg: /* What Expecco is Not */

2026-05-27T22:56:59Z

What Expecco is Not

← Nächstältere Version		Version vom 27. Mai 2026, 22:56 Uhr
Zeile 107:		Zeile 107:
	== What Expecco is Not ==		== What Expecco is Not ==

	Expecco is not a ready to run testsuite for a specific hard- or software system. Exept ~~may~~ help you or even provide such solution, but the majority of expecco users use it to write their own tests. Expecco provides a number of interfaces out of the box to interface to different systems and makes is very easy for users to add interfaces to even propriatrary systems, but there are no ready to execute tests provided. You as a user has to specify and define the test procedures, possibly with the help of the eXept team (if you wish), although expecco provides a lot of support to make this process as cost effective as possible. This includes AI support, inclusion of existing code or the import of textual test descriptions.		Expecco is not a ready to run testsuite for a specific hard- or software system. Exept will help you or even provide such solution or an initial framework, but the majority of expecco users use it to write their own tests. Expecco provides a number of interfaces out of the box to interface to different systems and makes is very easy for users to add interfaces to even propriatrary systems, but there are no ready to execute tests provided. You as a user has to specify and define the test procedures, possibly with the help of the eXept team (if you wish), although expecco provides a lot of support to make this process as cost effective as possible. This includes AI support, inclusion of existing code or the import of textual test descriptions.

	Our customer's test needs span a wide range from document processing, database and transaction processing, hardware interfacing to gui testings. But in any case, some initial effort is required to create building blocks for low level access, followed by actual creation of the high level test scenarios.		Our customer's test needs span a wide range from document processing, database and transaction processing, hardware interfacing to gui testings. But in any case, some initial effort is required to create building blocks for low level access, followed by actual creation of the high level test scenarios.

Cg: /* What Expecco is Not */

2026-05-27T22:50:08Z

What Expecco is Not

← Nächstältere Version		Version vom 27. Mai 2026, 22:50 Uhr
Zeile 107:		Zeile 107:
	== What Expecco is Not ==		== What Expecco is Not ==

	Expecco is not a ready to run testsuite for a specific hard- or software system. ~~Exepct~~ may help you or even provide such solution, but the ~~major~~ users of expecco		Expecco is not a ready to run testsuite for a specific hard- or software system. Exept may help you or even provide such solution, but the majority of expecco users use it to write their own tests. Expecco provides a number of interfaces out of the box to interface to different systems and makes is very easy for users to add interfaces to even propriatrary systems, but there are no ready to execute tests provided. You as a user has to specify and define the test procedures, possibly with the help of the eXept team (if you wish), although expecco provides a lot of support to make this process as cost effective as possible. This includes AI support, inclusion of existing code or the import of textual test descriptions.
	use it to write their own tests. Expecco provides a number of interfaces out of the box to interface to different systems and makes is very easy for users to add interfaces to even propriatrary systems, but there are no ready to execute tests provided. You as a user has to specify and define the test procedures, possibly with the help of the eXept team (if you wish).

	Our customer's test needs span a wide range from document processing, database and transaction processing, hardware interfacing to gui testings. But in any case, some initial effort is required to create building blocks for low level access, followed by actual creation of the high level test scenarios.		Our customer's test needs span a wide range from document processing, database and transaction processing, hardware interfacing to gui testings. But in any case, some initial effort is required to create building blocks for low level access, followed by actual creation of the high level test scenarios.

Cg am 27. Mai 2026 um 22:44 Uhr

2026-05-27T22:44:55Z

← Nächstältere Version		Version vom 27. Mai 2026, 22:44 Uhr
Zeile 104:		Zeile 104:
	== Expandability ==		== Expandability ==
	Custom action modules can use a large amount of freely available and already existing code. In this way, connections to protocols, hardware or document formats can be implemented quickly and at low cost. You can interactively integrate code fragments into your scenarios, which are written in JavaScript (Node.js/npm), Python, Java (jar files), C/C++, DotNET (assemblies), R (statistical evaluations), Gnuplot (create graphics) and many more.		Custom action modules can use a large amount of freely available and already existing code. In this way, connections to protocols, hardware or document formats can be implemented quickly and at low cost. You can interactively integrate code fragments into your scenarios, which are written in JavaScript (Node.js/npm), Python, Java (jar files), C/C++, DotNET (assemblies), R (statistical evaluations), Gnuplot (create graphics) and many more.

			== What Expecco is Not ==

			Expecco is not a ready to run testsuite for a specific hard- or software system. Exepct may help you or even provide such solution, but the major users of expecco
			use it to write their own tests. Expecco provides a number of interfaces out of the box to interface to different systems and makes is very easy for users to add interfaces to even propriatrary systems, but there are no ready to execute tests provided. You as a user has to specify and define the test procedures, possibly with the help of the eXept team (if you wish).

			Our customer's test needs span a wide range from document processing, database and transaction processing, hardware interfacing to gui testings. But in any case, some initial effort is required to create building blocks for low level access, followed by actual creation of the high level test scenarios.

			Do not expect to get an out-of-the-box ready to run product for your particular problem.

Cg: /* Erweiterbar */

2023-06-22T17:39:04Z

Erweiterbar

← Nächstältere Version		Version vom 22. Juni 2023, 17:39 Uhr
Zeile 102:		Zeile 102:
	In practice, there will be a division of tasks: for the connection to the tested system (SUT - System under Test), special action modules are often required, which a programmer will develop (e.g. connections to protocols, hardware or document formats). The flow of the test scenarios is then defined jointly by developers, testers and analysts using diagrams at a higher abstraction level, with no programming know-how being required for this.		In practice, there will be a division of tasks: for the connection to the tested system (SUT - System under Test), special action modules are often required, which a programmer will develop (e.g. connections to protocols, hardware or document formats). The flow of the test scenarios is then defined jointly by developers, testers and analysts using diagrams at a higher abstraction level, with no programming know-how being required for this.

	== ~~Erweiterbar~~ ==		== Expandability ==
	~~Eigene~~ ~~Aktionsbausteine~~ ~~können~~ ~~eine~~ ~~große~~ ~~Menge~~ an ~~frei~~ ~~verfügbarem~~ ~~und~~ ~~bereits~~ ~~existierenden~~ ~~Code~~ ~~nutzen~~. ~~Somit~~ ~~können~~ ~~Anbindungen~~ an ~~Protokolle~~, ~~Hardware~~ ~~oder~~ ~~Dokumentformate~~ ~~schnell~~ ~~und~~ ~~preisgünstig~~ ~~realisiert~~ ~~werden~~. ~~Sie~~ ~~können~~ ~~interaktiv~~ ~~Codefragmente~~ in ~~ihre~~ ~~Szenarien~~ ~~einbinden~~, ~~welche~~ in JavaScript (Node.js/npm), Python, Java (jar~~-Dateien~~), DotNET (~~Assemblies~~), R (~~statistische~~ ~~Auswertungen~~), Gnuplot (~~Grafiken~~ ~~erstellen~~) ~~u.a.m.~~ ~~erstellt~~ ~~wurden~~.		Custom action modules can use a large amount of freely available and already existing code. In this way, connections to protocols, hardware or document formats can be implemented quickly and at low cost. You can interactively integrate code fragments into your scenarios, which are written in JavaScript (Node.js/npm), Python, Java (jar files), C/C++, DotNET (assemblies), R (statistical evaluations), Gnuplot (create graphics) and many more.
	Für diese Programmiersprachen gibt es eine große Menge an frei verfügbaren oder auch lizensierbaren Programmpaketen, z.B. in github oder als npm (Node.js) bzw. pip (Python) Pakete.

Cg: /* Konzept */

2023-06-22T17:36:58Z

Konzept

← Nächstältere Version		Version vom 22. Juni 2023, 17:36 Uhr
Zeile 89:		Zeile 89:
	(or as PDF: [[Datei:expeccoArchitecture1.pdf]])		(or as PDF: [[Datei:expeccoArchitecture1.pdf]])

	== ~~Konzept~~ ==		== Concept ==
			The basic philosophy of Expecco is that test procedures can be created, maintained and executed by developers and programmers as well as by domain experts and analysts.
	Die Grundphilosophie von Expecco ist, daß Testabläufe sowohl von Entwicklern und Programmierern, als auch von Domänenexperten und Analysten erstellt, gewartet und ausgeführt werden können,
			without the need for special programming knowledge.
	ohne daß dazu spezielle Programmierkenntnisse notwendig wären.
			However, there must be no restrictions, and an experienced user has all the means at his disposal to create his own code, scripts and advanced functions.
	Dabei darf es aber keine Einschränkungen geben, und ein erfahrener Nutzer hat alle Mittel zur Verfügung, um eigenen Code, Scripte und erweiterte Funktionen zu erstellen.

			In order to meet both requirements, processes in Expecco can be defined both as activity diagrams ("boxes and arrows") and as script code in various programming languages.
	Um beiden Anforderungen gerecht zu werden, können Abläufe in Expecco sowohl als Aktivitätsdiagramm ("''Kästchen und Pfeile''") als auch als Scriptcode in verschiedenen Programmiersprachen definiert werden.
			This enables a "''Best of both worlds''" approach: on the one hand, non-programmers can connect existing action modules to complex scenarios at a high level of abstraction using "''Drag & Drop''" or recording of GUI actions,
	Die ermöglicht einen "''Best of both Worlds''" Ansatz: einerseits können Nichtprogrammierer auf einer hohen Abstraktionsebene bestehende Aktionsbausteine mittels "''Drag & Drop''" oder Recording von GUI Aktionen zu komplexen Szenarien verbinden,
	~~andererseits~~ ~~ist~~ es ~~möglich~~, ~~fehlende~~ ~~Funktionsbausteine~~ ~~als~~ ~~Scriptcode~~ zu ~~erstellen,~~ ~~und~~ ~~als~~ ~~Aktionsbaustein~~ ~~für~~ ~~andere~~ ~~Aktionen~~ ~~bereit~~ zu ~~stellen~~. ~~Wobei~~ "~~Scriptcode~~" ~~hier~~ ~~für~~ JavaScript, Python, Java, Shell/Batch ~~bis~~ ~~hin zu~~ C/C++ ~~steht~~.		on the other hand, it is possible to create missing function modules as script code and make them available as action modules for other actions. Where "script code" stands for JavaScript, Python, Java, Shell/Batch up to C/C++.

			"Hardcore" developers can of course also define the entire test procedure as a script/program code - however, this may result in the comprehensibility and modular usability being more or less lost for non-programmers. We therefore generally advise only using program code to encapsulate connections to existing frameworks and formulating the actual process as an activity diagram.
	"Hardcore" Entwickler können selbstverständlich auch den gesamten Testablauf als Script/Programmcode definieren - allerdings geht dadurch u.U. die Verständlichkeit und modulare Nutzbarkeit für Nichtprogrammierer mehr oder weniger verloren. Wir raten daher im Allgemeinen dazu, Programmcode nur zu verwenden, um Anbindungen an bestehende Frameworks zu kapseln, und den eigentlichen Ablauf als Aktivitätsdiagramm zu formulieren.

			In practice, there will be a division of tasks: for the connection to the tested system (SUT - System under Test), special action modules are often required, which a programmer will develop (e.g. connections to protocols, hardware or document formats). The flow of the test scenarios is then defined jointly by developers, testers and analysts using diagrams at a higher abstraction level, with no programming know-how being required for this.
	In der Praxis wird es zu einer Aufgabenteilung kommen: für die Anbindung an das getestete System (SUT - System under Test) werden oft spezielle Aktionsbausteine benötigt, die ein Programmierer entwickeln wird (z.B. Anbindungen an Protokolle, Hardware oder Dokumentformate). Der Ablauf der Testszenarien wird dann gemeinsam von Entwicklern, Testern und Analysten durch Diagramme auf einer höheren Abstaktionsebene definiert, wobei hierzu kein Programmierknowhow benötigt wird.

	== Erweiterbar ==		== Erweiterbar ==

Cg: /* Architecture */

2023-06-22T17:11:53Z

Architecture

← Nächstältere Version		Version vom 22. Juni 2023, 17:11 Uhr
Zeile 81:		Zeile 81:
	However, it allows "code injection" for Java, .NET and Python applications, thus "grey box" and "white box" tests are also possible.		However, it allows "code injection" for Java, .NET and Python applications, thus "grey box" and "white box" tests are also possible.

	In expecco, test scenarios can be formulated on a high level of ~~abstractionas~~ (activity) diagrams, as "keyword-driven" test sequences or as textual scripts in various programming languages. Scripts can be executed in expecco itself as well as in the [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] or other machines (e.g. to stimulate the SUT or to generate load).		In expecco, test scenarios can be formulated on a high level of abstraction as (activity) diagrams, as "keyword-driven" test sequences or as textual scripts in various programming languages. Scripts can be executed in expecco itself as well as in the [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] or other machines (e.g. to stimulate the SUT or to generate load).

	The following rough architecture picture gives an overview (not all available plugins are included):		The following rough architecture picture gives an overview (not all available plugins are included):

Cg: /* Architektur */

2023-06-22T17:11:23Z

Architektur

← Nächstältere Version		Version vom 22. Juni 2023, 17:11 Uhr
Zeile 76:		Zeile 76:
	expecco licenses are available as single user (node-lock or dongle), floating user (using a license manager) or company licenses. expecco can be used in isolated environments without access to a company network or the internet (using single-user or detached license server licenses). Please contact eXept for pricing and conditions.		expecco licenses are available as single user (node-lock or dongle), floating user (using a license manager) or company licenses. expecco can be used in isolated environments without access to a company network or the internet (using single-user or detached license server licenses). Please contact eXept for pricing and conditions.

	== ~~Architektur~~ ==		== Architecture ==

	Im ~~Prinzip ist~~ expecco ~~ein~~ "~~Black~~ ~~Box~~" ~~Testsystem~~, ~~welches~~ ~~keine~~ ~~Instrumentierung~~ ~~des~~ ~~getesteten~~ ~~Systems~~ ([[Glossary/en#SUT_.28System_Under_Test.29\|SUT = "System Under Test"]]) ~~erwartet oder benötigt~~ (d.h. es ~~ist~~ ~~nicht~~ ~~notwendig,~~ ~~das~~ [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] ~~mit~~ ~~speziellem~~ ~~Code~~ zu ~~erweitern~~ ~~oder~~ ~~spezielle~~ ~~Bibliotheken~~ ~~dazu zubinden~~).		In principle, expecco is a "black box" test system, which does not expect or require any instrumentation of the tested system ([[Glossary/en#SUT_.28System_Under_Test.29\|SUT = "System Under Test"]]) (i.e. it is not necessary to extend the [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] with special code or link special libraries to it).
	Es ~~ermöglicht~~ ~~aber~~ "code injection" ~~bei~~ Java-, .NET- ~~und~~ ~~PythonAnwendungen~~, ~~wodurch~~ "~~Grey~~ ~~Box~~" ~~und~~ "~~White~~ ~~Box~~" ~~Tests~~ ~~ebenfalls~~ ~~unterstützt~~ ~~werden~~.		However, it allows "code injection" for Java, .NET and Python applications, thus "grey box" and "white box" tests are also possible.

	~~Testszenarien~~ ~~können~~ in ~~expecco~~ ~~sowohl~~ ~~auf~~ ~~einer~~ ~~hohen~~ ~~Abstraktionsebene~~ ~~als~~ (~~Aktivitäts-~~) ~~Diagramme~~, ~~als~~ "~~Keyword~~-~~Driven~~" ~~Testsequenzen~~ ~~oder~~ ~~als~~ ~~textuelle~~ ~~Skripte~~ in ~~verschiedenen~~ ~~Programmiersprachen~~ ~~formuliert werden~~. ~~Skripte~~ ~~können~~ ~~sowohl~~ in expecco ~~selbst,~~ ~~als~~ ~~auch~~ im [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] ~~oder~~ ~~anderen~~ ~~Maschinen ausgeführt werden~~ (z.B. um ~~das~~ SUT ~~zu stimulieren, oder um~~ ~~Last~~ zu ~~generieren~~).		In expecco, test scenarios can be formulated on a high level of abstractionas (activity) diagrams, as "keyword-driven" test sequences or as textual scripts in various programming languages. Scripts can be executed in expecco itself as well as in the [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] or other machines (e.g. to stimulate the SUT or to generate load).

			The following rough architecture picture gives an overview (not all available plugins are included):

		⚫	[[Datei:expeccoArchitecture1.png\|1000px\|thumb\|left\|expecco architecture (not all plugins shown)]]

		⚫	(or as PDF: [[Datei:expeccoArchitecture1.pdf]])
	Folgendes grobes Architekturbild gibt dazu eine Übersicht (nicht alle verfügbaren Plugins sind darin enthalten):

⚫	[[Datei:expeccoArchitecture1.png\|1000px\|thumb\|left\|expecco ~~Architektur~~ (~~nicht~~ ~~alle~~ ~~Plugins~~ ~~dargestellt~~)]]

⚫	(~~oder~~ ~~als~~ PDF: [[Datei:expeccoArchitecture1.pdf]])

	== Konzept ==		== Konzept ==

Cg: /* Plugins */

2023-06-22T17:06:39Z

Plugins

← Nächstältere Version		Version vom 22. Juni 2023, 17:06 Uhr
Zeile 67:		Zeile 67:
	* Jira Plugin, to create issues in a Jira system		* Jira Plugin, to create issues in a Jira system
	* expecco ALM plugin to interface with our own QM/Test center		* expecco ALM plugin to interface with our own QM/Test center

	Some plugins are already included in the base system (Selenium, expecco ALM), others need to be licensed separately.

	== Availability ==		== Availability ==

Cg: /* Plugins */

2023-06-22T17:06:20Z

Plugins

← Nächstältere Version		Version vom 22. Juni 2023, 17:06 Uhr
Zeile 52:		Zeile 52:
	* GUI Test of VisualWorks applications		* GUI Test of VisualWorks applications
	* GUI Test for VNC connections		* GUI Test for VNC connections
	* ~~Interfacing~~ to CAN bus systems (automotive)		* Interface to CAN bus systems (automotive)
	* ~~Interfacing~~ to SomeIP (automotive)		* Interface to SomeIP brokers/clients (automotive)
	* ~~Interfacing~~ to EDIFACT and SWIFT systems (finance)		* Interface to EDIFACT and SWIFT systems (B2B, finance)
	* ~~Interfacing~~ to MQTT or OPC systems (manufacturing, ~~Internet of~~ ~~Things~~)		* Interface to MQTT and OPC systems (manufacturing, IoT, automotive)
			* Integration and execution of functional mockup units (FMU)
			* Import of test specifications (eg. from Excel- or Word documents)
			* Interfaces to specific lab equipment (telecom, automotive)

	Plugins typically consist of additional dll- and block libraries that provide the domain specific functions as ready-to-use building blocks. These are inserted into test sequences via drag & drop.		Plugins typically consist of additional dll- and block libraries that provide the domain specific functions as ready-to-use building blocks. These are inserted into test sequences via drag & drop. The GUI plugins include recording functions, so that user sessions are immediately available as an executable activity diagram.

	Other plugins provide integration into the existing QM infrastructure:		Other plugins provide integration into the existing QM infrastructure:

Cg: /* Plugins */

2023-06-22T16:59:53Z

Plugins

← Nächstältere Version		Version vom 22. Juni 2023, 16:59 Uhr
Zeile 52:		Zeile 52:
	* GUI Test of VisualWorks applications		* GUI Test of VisualWorks applications
	* GUI Test for VNC connections		* GUI Test for VNC connections
	* Webtest using Selenium/WebDriver for Chrome, Firefox, IE, Edge, Safari, Opera and other browsers
	* Interfacing to CAN bus systems (automotive)		* Interfacing to CAN bus systems (automotive)
	* Interfacing to SomeIP (automotive)		* Interfacing to SomeIP (automotive)