expecco Wiki (Version 25.x) - Letzte Änderungen [de]

Expecco API/en

Cg — Thu, 25 Jun 2026 07:14:22 GMT

Pin Value

← Nächstältere Version		Version vom 25. Juni 2026, 07:14 Uhr
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 3.984:		Zeile 3.984:

	*jsonObject '''jsonValueIfPresent''' (''inPin'') <br>Returns the pin-datum as a [[Embedded_Systems_C_Bridge_API#JSON_Library\|jsonObject]] if it has one, NULL otherwise. Similar to "<code>jsonValue()</code>", but avoids the exception. The returned pointer becomes invalid after the action's execution.		*jsonObject '''jsonValueIfPresent''' (''inPin'') <br>Returns the pin-datum as a [[Embedded_Systems_C_Bridge_API#JSON_Library\|jsonObject]] if it has one, NULL otherwise. Similar to "<code>jsonValue()</code>", but avoids the exception. The returned pointer becomes invalid after the action's execution.

			void '''keepValue''' (''inPin'') <br> (rel. 26.1) Returns a pointer to the malloc's bulk data and tells the bridge that the underlying memory shall NOT be freed when execute() returns.
			This avoids the need to memcpy big data blocks from the incoming memory buffer; however it is now in your responsibility to free that memory eventually.<br>
			This is only to be used for strings, bytearrays and other vectors.

	Variable number of input/output pins are not supported. You should pass an array or structure if required.		Variable number of input/output pins are not supported. You should pass an array or structure if required.
Zeile 4.148:		Zeile 4.152:
	If a huge number of data elements (known as "''Bulk Data''") are to be transferred, transmission times may get much longer than the actual execution time of the action (keep in mind that the communication times take most of the time if the executed computation is simple).		If a huge number of data elements (known as "''Bulk Data''") are to be transferred, transmission times may get much longer than the actual execution time of the action (keep in mind that the communication times take most of the time if the executed computation is simple).

		⚫	If the cBridge runs on the same machine as expecco, shared memory will be used to exchange bulk data. This may reduce the transmission times drastically, depending on the amount of data (there are still other messages exchanged via the socket communication).
	There are multiple possible ways to deal with this situation:

			===== Data from C to Expecco =====
	* Passing a Pointer to expecco		* Passing a Pointer to expecco
	:if you can leave the data inside the bridge (eg. as malloc'd data vector), '''and''' expecco does not need to access the elements of the vector, you can leave the data inside the cBridge and only pass a handle to expecco. This handle may later be sent to another C-action (on the same bridge) to process the data at non-critical times (eg. at the end of the test).		:if you can leave the data inside the bridge (eg. as malloc'd data vector), '''and''' expecco does not need to access the elements of the vector, you can leave the data inside the cBridge and only pass a handle to expecco. This handle may later be sent to another C-action (on the same bridge) to process the data at non-critical times (eg. at the end of the test).
Zeile 4.161:		Zeile 4.166:
	:This is probably the fastest method to transmit bytes, but comes with those possible pitfalls. We therefore recommend to try the "Bulk Data as Vector" method first. In most situations that is either within the acceptable timing constraints, or too far off, such that the ByteArray transmission will also not be fast enough, and you should use the pointer passing method anyway.		:This is probably the fastest method to transmit bytes, but comes with those possible pitfalls. We therefore recommend to try the "Bulk Data as Vector" method first. In most situations that is either within the acceptable timing constraints, or too far off, such that the ByteArray transmission will also not be fast enough, and you should use the pointer passing method anyway.

			===== Passing Data from Expecco to C =====
⚫	If the cBridge runs on the same machine as expecco, shared memory will be used to exchange bulk data. This may reduce the transmission times drastically, depending on the amount of data (there are still other messages exchanged via the socket communication).
			Be aware that the bulk data pointer you receive at an input pin has been allocated
			in malloc'd memory which is freed when the execute() function returns. If the data is to be retained inside the C bridge (or passed to a function which keeps a reference), you have two choices:
			* memcpy the data into an internal buffer
			* tell the caller that the buld data should not be freed on return from execute
			The second variant is available with expecco 26.1, and preferred.<br>In either case, it is in your responsibility to free the memory when no longer needed.

	<small><sup>1)</sup></small>Starting with expecco 26.2, this is no longer required - there are now additional fast bulk transfer entries named: <code>putFloatsN</code>, <code>putDoublesN</code> etc.		<small><sup>1)</sup></small>Starting with expecco 26.1, this is no longer required - there are now additional fast bulk transfer entries named: <code>putFloatsN</code>, <code>putDoublesN</code> etc.

	=== Example1: Writing and Calling C Code in Expecco ===		=== Example1: Writing and Calling C Code in Expecco ===

Release Notes 26.x

Alkurz — Wed, 24 Jun 2026 09:39:00 GMT

Release 26.1 (Q2 2026)

← Nächstältere Version		Version vom 24. Juni 2026, 09:39 Uhr
Zeile 17:		Zeile 17:
	* Feature: SSH builtin, plus SSH and SFTP clients (both via [[Tools_FileBrowser/en\|FileBrowser]])		* Feature: SSH builtin, plus SSH and SFTP clients (both via [[Tools_FileBrowser/en\|FileBrowser]])
	* Feature: public/private keypair generation via a [[Tools_FileBrowser/en\|FileBrowser]] menu (for easy SSH setup)		* Feature: public/private keypair generation via a [[Tools_FileBrowser/en\|FileBrowser]] menu (for easy SSH setup)
			* Improvement: Bundled python3 installer updated to version 3.13.14
	* Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions\|Delivered versions for QT and build environment]])		* Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions\|Delivered versions for QT and build environment]])
	* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.		* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.

KI Coding Plugin

Cg — Tue, 23 Jun 2026 13:16:42 GMT

LLaMa.cpp

← Nächstältere Version		Version vom 23. Juni 2026, 13:16 Uhr
Zeile 390:		Zeile 390:
	llama-server.exe -hf unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF:Q4_K_M		llama-server.exe -hf unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF:Q4_K_M

	Das Modell läuft auf der lokalen CPU (Laptop, ohne GPU), und zeigt dabei ~~ein~~ ~~hervorragende~~ Antworten (wenn man Geduld hat). Zugegeben, wir haben auch einiges an Wissen in den Speicher vorgepackt.		Das Modell läuft auf der lokalen CPU (Laptop, ohne GPU), und zeigt dabei durchaus gute Antworten (wenn man Geduld hat). Zugegeben, wir haben auch einiges an Wissen in den Speicher vorgepackt.

	Im expecco Chat Fenster:		Im expecco Chat Fenster:

CVS Plugin/en

Robin — Tue, 23 Jun 2026 09:02:07 GMT

Introduction

← Nächstältere Version		Version vom 23. Juni 2026, 09:02 Uhr
Zeile 2:		Zeile 2:

	The plugin provides a user freindly interface to cvs, for managing expecco testsuites in a CVS repository (version management system).		The plugin provides a user freindly interface to cvs, for managing expecco testsuites in a CVS repository (version management system).
	~~THe~~ typical operations to checkin/checkout/compare/merge revisions are provided via convenient menu functions in expecco's "Plugin" → "Productivity" → "CVS" menu.		The typical operations to checkin/checkout/compare/merge revisions are provided via convenient menu functions in expecco's "Plugin" → "Productivity" → "CVS" menu.

	=== Prerequisites ===		=== Prerequisites ===

Benutzer:Robin

Sv — Tue, 23 Jun 2026 08:02:08 GMT

Benutzerkonto Robin wurde von Sv erstellt und das Passwort wurde per E-Mail zugesandt

KI Coding Plugin

Cg — Sat, 20 Jun 2026 13:06:21 GMT

LLaMa.cpp

Änderungen zeigen

Expecco API/en

Cg — Fri, 19 Jun 2026 23:47:26 GMT

Environment Access (Bridged Scheme)

KI Coding Plugin

Sv — Fri, 19 Jun 2026 13:11:46 GMT

add AI Coding license-feature note at top

@@ Zeile 1: / Zeile 1: @@
 = KI Coding Plugin =
 Das KI Coding Plugin bindet einen Large Language Model (LLM) basierten
@@ Zeile 122: / Zeile 124: @@
 == Coding Assistenten ==
 === Claude Code ===
@@ Zeile 157: / Zeile 161: @@
 Sollten Sie ein Komma vergessen haben wird beim Start eine Fehlermeldung erscheinen. Mit "/mcps" sollten die beiden aufgelistet werden.
 === Tabnine ===
 == Tipps ==

KI Coding Plugin

Cg — Fri, 19 Jun 2026 10:16:59 GMT

Versuche mit qwen2.5-coder:7b

@@ Zeile 117: / Zeile 117: @@
 als Kontext versendet.
-Bei Benutzung von Anthropic API-Tokens - wie hier der Fall - werden laut Anthropic die Daten nicht zum Training des KI-Modells genutzt ([https://privacy.claude.com/de/articles/7996868-werden-meine-daten-fur-das-modelltraining-verwendet Anthropic Erkärung dazu]). Für die Wahrheit dieser Aussage könne wir nicht garantieren und haften.
+Bei Benutzung von Anthropic API-Tokens - wie hier der Fall - werden laut Anthropic die Daten nicht zum Training des KI-Modells genutzt ([https://privacy.claude.com/de/articles/7996868-werden-meine-daten-fur-das-modelltraining-verwendet Anthropic Erkärung dazu]).<br>Für die Wahrheit dieser Aussage können wir nicht garantieren und haften.<br>Zu bedenken ist auch, daß die KI-Modelle nicht in inländischen Rechenzentren laufen, und eventuell weitere "Mitleser" involviert sind. Dies gilt insbesondere für Hightech, KI, Software und Defence Unternehmen, wo Fälle von Wirtschaftsspionage bekannt sind.
-Wenn Sie sicher sein wollen, daß keine Information Ihr Haus verlässt empfehlen wir eine eigenem geschlossene in-house KI Umgebung, wie sie bei einigen unserer Kunden bereits existiert. Sie dürfen dann selbstverständlich nur die URLs dieser Umgebung konfigurieren. Expecco kommuniziert ausschließlich mit der von Ihnen eingegebenen KI.
+⚠ Wenn Sie sicher sein wollen, daß keine Information Ihr Haus verlässt empfehlen wir eine eigenem geschlossene in-House KI Umgebung, wie sie bei einigen unserer Kunden bereits existiert. Sie dürfen dann selbstverständlich nur die URLs dieser Umgebung konfigurieren. Expecco kommuniziert ausschließlich mit der von Ihnen eingegebenen KI.
 == Tipps ==
@@ Zeile 125: / Zeile 165: @@
 * '''Mehrere Konversationen''': der Chat ist ein Singleton — eine neue Anfrage über ein Browser-/Editor-Menü startet jedesmal eine '''neue''' Konversation. Folge-Fragen (Klärung, Vertiefung) gehen über das Eingabefeld in derselben Konversation.
 * '''Vorsicht:''' Die Größe der übertragenen Daten (auch die aus dem Chatfenster) geht in die Kostenberechnung ein. Deshalb immer eine neue Konversation starten, wenn es um ein neues Thema geht.
-* '''Modell wechseln''': Für schnelle Routine-Antworten Sonnet, für schwierige Refactorings Opus. Über das '''Set model'''-Untermenü direkt aus der Toolbar oder über die Settings.
+* '''Modell wechseln''': Für schnelle Routine-Antworten Haiku oder Sonnet, für schwierige Refactorings Opus. Über das '''Set model'''-Untermenü direkt aus der Toolbar oder über die Settings.
 * '''Anbieter wechseln''': Sind Schlüssel für beide Anbieter konfiguriert, schaltet das '''Set provider'''-Untermenü ohne Umweg über den Settings-Dialog um.
 * '''Code direkt ausführen''': In Code-Karten kann markierter Smalltalk-Code per doIt / printIt / inspectIt direkt evaluiert werden — praktisch z.B. um vom Modell vorgeschlagene SUnit-Asserts gleich auszuprobieren, ohne den Code erst in einen Workspace zu kopieren.
@@ Zeile 131: / Zeile 171: @@
 == Tipps für die Arbeit mit claudeCode ==
-Wenn Sie claudeCode verwenden, stehen ihnen noch weit mehr Funktionen zur Verfügung: sie können zum Beispiel im claudeCode Terminal eingeben:
+Wenn Sie ClaudeCode oder Opencode verwenden, stehen ihnen noch weit mehr Funktionen zur Verfügung: sie können zum Beispiel im claudeCode Terminal eingeben:
 * "mach mir eine neue Suite in einem neuen Fenster",
 * "Mache eine Aktion zur Berechnung des Umfangs eines Kreises bei gegebenen Radius",
@@ Zeile 291: / Zeile 331: @@
 === Versuche mit qwen2.5-coder:7b ===
-Dieser zeigt erstaunlich gute Antworten auf unserer lokalen ollama installtaion mit einer (ncah heutigem Maßstab) durchschnittlichen GPU (Preis heute ca. 1500.-)
+Dieser zeigt erstaunlich gute Antworten auf unserer lokalen ollama installtaion mit einer (nach heutigem Maßstab) durchschnittlichen GPU (Preis heute ca. 1500.-)
 == Wahl der Modellgrösse ==

← Nächstältere Version		Version vom 19. Juni 2026, 23:47 Uhr
(11 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 4.597:		Zeile 4.597:
	==== Reporting (Bridged Scheme) ====		==== Reporting (Bridged Scheme) ====

	*'''error'''(''infoString'' [ ,''arg1'' ... ~~,''arg4''~~ ]) <br>Report a defect (in the test). ~~Up to 4 optional~~ args are sliced into the string, if it contains "%i" placeholders. Stops execution.		*('''error''' ''infoString'' [ ''arg1'' ... ]) <br>Report a defect (in the test). Optional args are sliced into the string, if it contains "%i" placeholders. Stops execution.

	*'''fail'''(''infoString'' [ ,''arg1'' ... ~~,''arg4''~~ ]) <br>Report a failure (in the SUT). Stops execution.		*('''fail''' ''infoString'' [ ''arg1'' ... ]) <br>Report a failure (in the SUT). Stops execution.

	*'''inconclusive'''(''infoString'' [ ,''arg1'' ... ~~,''arg4''~~ ]) <br>Report an inconclusive test. Stops execution.		*('''inconclusive''' ''infoString'' [ ''arg1'' ... ]) <br>Report an inconclusive test. Stops execution.

	*'''activitySuccess'''(''infoString'' [ ,''arg1'' ... ~~,''arg4''~~ ]) <br>Finishes the current activity with success (same as "success()").		*('''activitySuccess''' ''infoString'' [ ''arg1'' ... ]) <br>Finishes the current activity with success (same as "success()").

	*'''pass'''(''infoString'' [ ,''arg1'' ... ~~,''arg4''~~ ]) <br>Finishes the current testCase with success.		*('''pass''' ''infoString'' [ ''arg1'' ... ]) <br>Finishes the current testCase with success.


Zeile 4.630:		Zeile 4.630:

	--- unfinished --		--- unfinished --
	*'''confirm'''(''msg'')<br>Opens a simple yes/no dialog; returns a boolean.		*('''confirm''' ''msg'')<br>Opens a simple yes/no dialog; returns a boolean.

	*'''request'''(''msg'')<br>Opens a simple string-input dialog; returns a string or nil if cancel was pressed.		*('''request''' ''msg'')<br>Opens a simple string-input dialog; returns a string or nil if cancel was pressed.

	*'''requestPassword'''(''msg'')<br>same, but the entered string is not shown on the screen		*('''requestPassword''' ''msg'')<br>same, but the entered string is not shown on the screen

	*'''requestFilename'''(''msg'')<br>asks for a filename		*('''requestFilename''' ''msg'')<br>asks for a filename


	==== Logging (Bridged Scheme) ====		==== Logging (Bridged Scheme) ====

	*'''logFail'''(''messageString'') <br>Adds a fail message to the activity log.		*('''logFail''' ''messageString'') <br>Adds a fail message to the activity log.

	*'''logError'''(''messageString'') <br>Adds a error message to the activity log.		*('''logError''' ''messageString'') <br>Adds a error message to the activity log.

	*'''logWarning'''(''messageString'') <br>Adds a warning to the activity log.		*('''logWarning''' ''messageString'') <br>Adds a warning to the activity log.

	*'''logInfo'''(''messageString'') <br>Adds an info message to the activity log.		*('''logInfo''' ''messageString'') <br>Adds an info message to the activity log.

	*'''alert'''(''messageString'')<br>Adds a warning message to the activity log, and also shows a DialogBox, which has to be confirmed by the operator. The dialog box and confirmation can be disabled by a settings flag in the "''Execution''" → "''Log Settings''" dialog (by default it is disabled).		*('''alert''' ''messageString'')<br>Adds a warning message to the activity log, and also shows a DialogBox, which has to be confirmed by the operator. The dialog box and confirmation can be disabled by a settings flag in the "''Execution''" → "''Log Settings''" dialog (by default it is disabled).

	*'''warn'''(''messageString'')<br>Same as ''alert:'' (for JavaScript compatibility).		*('''warn''' ''messageString'')<br>Same as ''alert:'' (for JavaScript compatibility).


	==== Environment Access (Bridged Scheme) ====		==== Environment Access (Bridged Scheme) ====
	*'''environmentAt'''(<varName>);<br>Fetches and returns a value from the expecco environment which is in scope of the current activity.<br>You can only read simple objects (numbers, booleans and strings) from ruby actions.		*('''environmentAt''' <varName>)<br>Fetches and returns a value from the expecco environment which is in scope of the current activity.<br>You can only read simple objects (numbers, booleans and strings) from ruby actions.

	*'''environmentAtPut'''(<varName>, <newValue>);<br>Writes a value into the expecco environment which is in scope of the current activity.<br>The variable must be writable.<br>You can only write simple objects (numbers, booleans and strings) from ruby actions.		*('''environmentAtPut!''' <varName> <newValue>)<br>Writes a value into the expecco environment which is in scope of the current activity.<br>The variable must be writable.<br>You can only write simple objects (numbers, booleans and strings) from ruby actions.
	<!--		<!--
	*'''eval''' (''smalltalkCodeString'') <br>Evaluate a piece of Smalltalk code inside expecco.		*'''eval''' (''smalltalkCodeString'') <br>Evaluate a piece of Smalltalk code inside expecco.
Zeile 4.666:		Zeile 4.667:
	==== Input Pins (Bridged Scheme) ====		==== Input Pins (Bridged Scheme) ====

	*('''pin-hasValue? ''pin'')<br>Returns #tif the pin has received a value		*('''pin-hasValue?''' ''pin'')<br>Returns #tif the pin has received a value

	*('''pin-value ''pin'')<br>Returns the value of the pin. Raises an error if the pin did not receive any value.		*('''pin-value''' ''pin'')<br>Returns the value of the pin. Raises an error if the pin did not receive any value.

	*('''pin-valueIfAbsent''' ''pin'' ''alternativeValue'') <br>Returns the value of a pin or the value from alternativeValue if the pin did not receive any value.		*('''pin-valueIfAbsent''' ''pin'' ''alternativeValue'') <br>Returns the value of a pin or the value from alternativeValue if the pin did not receive any value.
Zeile 4.679:		Zeile 4.680:
	==== Output Pins (Bridged Scheme) ====		==== Output Pins (Bridged Scheme) ====

	*''pin''.'''~~value~~'''(''someValue'')<br>Writes the value to the pin. Only simple object can be transferred by value (nil, booleans, integers, floats, strings).<br>Anything else should be passed by reference (see <code>makeRef</code> below).		*('''pin-value!''' ''pin'' ''someValue'')<br>Writes the value to the pin. Only simple object can be transferred by value (nil, booleans, integers, floats, strings).<br>Anything else should be passed by reference (see <code>makeRef</code> below).


	==== Passing Objects by Reference (Bridged Scheme) ====		==== Passing Objects by Reference (Bridged Scheme) ====
	By default, objects written to output pins via "'''value:'''" will be marshalled to JSON, transferred to expecco and decoded there.		By default, objects written to output pins via "('''pin-value!''' ...)" will be marshalled to JSON, transferred to expecco and decoded there.
	Effectively, a copy of the object is created, which looses its identity when sent back later to the remote ruby in another action.		Effectively, a copy of the object is created, which looses its identity when sent back later to the remote ruby in another action.
	This would make it impossible to get a handle from a remote action, which is to be sent to another action on the same remote machine.		This would make it impossible to get a handle from a remote action, which is to be sent to another action on the same remote machine.
	The "<code>makeRef</code>" method solves this, by creating a "pointer" or "handle" to the object inside the remote machine.		The "<code>makeRef</code>" method solves this, by creating a "pointer" or "handle" to the object inside the remote machine.

	*'''makeRef'''(''object'')<br>creates a reference object, which can be written to a pin.		*('''makeRef''' ''object'')<br>creates a reference object, which can be written to a pin.

	*'''makeRef'''(''object'', '''name''')<br>ditto, but gives it a user friendly name (eg. for the expecco log)		*('''makeRef''' ''object'', '''name''')<br>ditto, but gives it a user friendly name (eg. for the expecco log)
	:I.e. to write a reference to a pin, use:		:I.e. to write a reference to a pin, use:
	::: ''~~somePin~~''.'''~~value~~'''('''makeRef'''(''someObject''))		::: ('''pin-value!''' ''somePin'' '''('''makeRef''' ''someObject''))

	== DotNET Elementary Blocks ==		== DotNET Elementary Blocks ==