https://doc.expecco.de/api.php?action=feedcontributions&feedformat=atom&user=Caellwein 2026-04-26T00:58:24Z Benutzerbeiträge MediaWiki 1.44.2 https://doc.expecco.de/index.php?title=Settings_SeppMedPluginSettings/en&diff=5754 2015-12-02T09:59:10Z

<p>Caellwein: /* Test Action Name */</p> <hr /> <div>== Sepp Med Plugin Settings ==<br /> <br /> === Comments ===<br /> <br /> ==== Create log step for comment ====<br /> <br /> Uncheck if no log step should be created for each comment.<br /> <br /> ==== Background Color ====<br /> <br /> The backgound color for comment stept.<br /> <br /> ==== Test Action Name ====<br /> <br /> Adjust which step to create while importing.<br /> <br /> === Execution ===<br /> <br /> ==== Show Window for Print ====<br /> <br /> [[ Category: Settings ]]<br /> <br /> Determine how long a window is shown.</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SeppMedPluginSettings/en&diff=5753 2015-12-02T09:58:33Z

<p>Caellwein: /* Background Color */</p> <hr /> <div>== Sepp Med Plugin Settings ==<br /> <br /> === Comments ===<br /> <br /> ==== Create log step for comment ====<br /> <br /> Uncheck if no log step should be created for each comment.<br /> <br /> ==== Background Color ====<br /> <br /> The backgound color for comment stept.<br /> <br /> ==== Test Action Name ====<br /> <br /> === Execution ===<br /> <br /> ==== Show Window for Print ====<br /> <br /> [[ Category: Settings ]]<br /> <br /> Determine how long a window is shown.</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SeppMedPluginSettings/en&diff=5752 2015-12-02T09:58:13Z

<p>Caellwein: /* Create log step for comment */</p> <hr /> <div>== Sepp Med Plugin Settings ==<br /> <br /> === Comments ===<br /> <br /> ==== Create log step for comment ====<br /> <br /> Uncheck if no log step should be created for each comment.<br /> <br /> ==== Background Color ====<br /> <br /> ==== Test Action Name ====<br /> <br /> === Execution ===<br /> <br /> ==== Show Window for Print ====<br /> <br /> [[ Category: Settings ]]<br /> <br /> Determine how long a window is shown.</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SeppMedPluginSettings/en&diff=5751 2015-12-02T09:57:45Z

<p>Caellwein: /* Show Window for Print */</p> <hr /> <div>== Sepp Med Plugin Settings ==<br /> <br /> === Comments ===<br /> <br /> ==== Create log step for comment ====<br /> <br /> ==== Background Color ====<br /> <br /> ==== Test Action Name ====<br /> <br /> === Execution ===<br /> <br /> ==== Show Window for Print ====<br /> <br /> [[ Category: Settings ]]<br /> <br /> Determine how long a window is shown.</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SeppMedPluginSettings&diff=5750 2015-12-02T09:56:15Z

<p>Caellwein: Weiterleitung nach Settings SeppMedPluginSettings/en erstellt</p> <hr /> <div>#redirect [[ Settings SeppMedPluginSettings/en ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Kategorie:Settings&diff=5749 2015-12-02T09:55:45Z

<p>Caellwein: </p> <hr /> <div>* [[ Settings LanguageSettings]]<br /> * [[ Settings PrinterSettings]]<br /> * [[ Settings LookAndFeelSettings]]<br /> ** [[ Settings TreeSettings]]<br /> ** [[ Settings CodeEditorSettings]]<br /> *** [[ Settings SyntaxColorSettings]]<br /> ** [[ Settings WorksheetEditorSettings]]<br /> *** [[ Settings GeneralWorksheetEditorLookSettings]]<br /> *** [[ Settings WorksheetEditorElementLookSettings]]<br /> ** [[ TableDrivenBlock Settings]]<br /> ** [[ Settings TagColorSettings]]<br /> ** [[ Settings TagIconSettings]]<br /> ** [[ Settings StateColorSettings]]<br /> ** [[ Settings SoundSettings]]<br /> ** [[ Settings FontSettings]]<br /> ** [[ Settings HotKeySettings]]<br /> ** [[ Settings MiscLookSettings]]<br /> * [[ Settings ProjectManagementSettings]]<br /> ** [[ Settings ExpeccoNETSettings]]<br /> * [[ Settings ExecutionSettings]]<br /> ** [[ Settings LoggingSettings]]<br /> ** [[ Settings DebuggerSettings]]<br /> * [[ Settings ReportSettings]]<br /> ** [[ Settings StandardReportTemplateSettings]]<br /> ** [[ Settings CompanySettings]]<br /> * [[ Settings ExternalToolsSettings]]<br /> * [[ Settings UpdatesSettings]]<br /> * [[ Settings PluginSettings]]<br /> ** [[ Settings AndroidGUITestPluginSettings]]<br /> ** [[ Settings CommonJavaGUITestPluginSettings]]<br /> ** [[ Settings GUITestPlatformSettings]]<br /> ** [[ Settings GembirdPluginSettings]]<br /> ** [[ Settings JavaBridgePluginSettings]]<br /> ** [[ Settings ManualTestImport1PluginSettings]]<br /> ** [[ Settings ManualTestImport2PluginSettings]]<br /> ** [[ Settings SAPPluginSettings]]<br /> ** [[ Settings SeleniumPluginSettings]]<br /> ** [[ Settings VisualBasicScriptSettings]]<br /> ** [[ Settings WindowsAutomationPluginSettings]]<br /> ** [[ Settings XMImportPluginSettings]]<br /> ** [[ Settings SeppMedPluginSettings ]]<br /> * [[ Settings LicenseInstallation]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_VisualBasicScriptSettings/en&diff=5748 2015-12-02T09:54:35Z

<p>Caellwein: Die Seite wurde neu angelegt: „ == Visual Basic Script Plugin Settings == The Visual Basic Script Plugin can be used to create, import and execute Visual Basic Script files. This settings …“</p> <hr /> <div><br /> == Visual Basic Script Plugin Settings ==<br /> <br /> The Visual Basic Script Plugin can be used to create, import and execute Visual Basic Script files.<br /> <br /> This settings dialog is only shown/enabled if the plugin is loaded and licenced. <br /> <br /> === Settings ===<br /> <br /> ==== Scope ====<br /> <br /> To import Visual Basic Script Files the plugin does have a file browser. Using this scope the view of this file browser can be limited to a specific path.<br /> <br /> ==== Delete External Files ====<br /> <br /> If this checkbox is checked files from the file system can be deleted from the Visual Basic Script Plugin file browser.<br /> <br /> === Connection ===<br /> <br /> ==== Script Client ====<br /> <br /> The Plugin does use a middleware, the so called Script Client, to read and execute Script Files. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\vbScript\ScriptClient\ScriptClient.exe<br /> <br /> [[ Category: Settings ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_VisualBasicScriptSettings&diff=5747 2015-12-02T09:54:28Z

<p>Caellwein: Weiterleitung nach Settings VisualBasicScriptSettings/en erstellt</p> <hr /> <div>#redirect [[ Settings VisualBasicScriptSettings/en ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings&diff=5746 2015-12-02T09:53:45Z

<p>Caellwein: Weiterleitung nach Settings SAPPluginSettings/en erstellt</p> <hr /> <div>#redirect [[ Settings SAPPluginSettings/en ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings/en&diff=5745 2015-12-02T09:53:27Z

<p>Caellwein: </p> <hr /> <div>== SAP Plugin Settings ==<br /> <br /> The SAP Plugin can be used to interact with a SAP system via BAPI.<br /> <br /> === Connection ===<br /> <br /> ==== Java Middleware ====<br /> <br /> The Plugin does use a middleware, the so called Service Client, to communicate with SAP. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\sap\ServiceClient\ServiceClient.jar<br /> <br /> [[ Category: Settings ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings&diff=5744 2015-12-02T09:53:11Z

<p>Caellwein: </p> <hr /> <div>== SAP Plugin Settings ==<br /> <br /> The SAP Plugin can be used to interact with a SAP system via BAPI.<br /> <br /> === Connection ===<br /> <br /> ==== Java Middleware ====<br /> <br /> The Plugin does use a middleware, the so called Service Client, to communicate with SAP. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\sap\ServiceClient\ServiceClient.jar<br /> <br /> [[ Category: Settings ]]<br /> <br /> redirect [[ Settings SAPPluginSettings/en ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings&diff=5743 2015-12-02T09:52:41Z

<p>Caellwein: Weiterleitung nach Settings SAPPluginSettings/en erstellt</p> <hr /> <div>#redirect [[ Settings SAPPluginSettings/en ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings/en&diff=5742 2015-12-02T09:51:54Z

<p>Caellwein: Weiterleitung nach Settings SAPPluginSettings erstellt</p> <hr /> <div>#redirect [[ Settings SAPPluginSettings ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SeppMedPluginSettings/en&diff=5741 2015-12-02T09:50:34Z

<p>Caellwein: Die Seite wurde neu angelegt: „== Sepp Med Plugin Settings == === Comments === ==== Create log step for comment ==== ==== Background Color ==== ==== Test Action Name ==== === Execution …“</p> <hr /> <div>== Sepp Med Plugin Settings ==<br /> <br /> === Comments ===<br /> <br /> ==== Create log step for comment ====<br /> <br /> ==== Background Color ====<br /> <br /> ==== Test Action Name ====<br /> <br /> === Execution ===<br /> <br /> ==== Show Window for Print ====<br /> <br /> [[ Category: Settings ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings&diff=5740 2015-12-02T09:47:58Z

<p>Caellwein: </p> <hr /> <div>== SAP Plugin Settings ==<br /> <br /> The SAP Plugin can be used to interact with a SAP system via BAPI.<br /> <br /> === Connection ===<br /> <br /> ==== Java Middleware ====<br /> <br /> The Plugin does use a middleware, the so called Service Client, to communicate with SAP. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\sap\ServiceClient\ServiceClient.jar<br /> <br /> [[ Category: Settings ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_VisualBasicScriptSettings&diff=5739 2015-12-02T09:47:43Z

<p>Caellwein: </p> <hr /> <div>== Visual Basic Script Plugin Settings ==<br /> <br /> The Visual Basic Script Plugin can be used to create, import and execute Visual Basic Script files.<br /> <br /> This settings dialog is only shown/enabled if the plugin is loaded and licenced. <br /> <br /> === Settings ===<br /> <br /> ==== Scope ====<br /> <br /> To import Visual Basic Script Files the plugin does have a file browser. Using this scope the view of this file browser can be limited to a specific path.<br /> <br /> ==== Delete External Files ====<br /> <br /> If this checkbox is checked files from the file system can be deleted from the Visual Basic Script Plugin file browser.<br /> <br /> === Connection ===<br /> <br /> ==== Script Client ====<br /> <br /> The Plugin does use a middleware, the so called Script Client, to read and execute Script Files. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\vbScript\ScriptClient\ScriptClient.exe<br /> <br /> [[ Category: Settings ]]</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_SAPPluginSettings&diff=5738 2015-12-02T08:55:52Z

<p>Caellwein: Die Seite wurde neu angelegt: „== SAP Plugin Settings == The SAP Plugin can be used to interact with a SAP system via BAPI. === Connection === ==== Java Middleware ==== The Plugin does u…“</p> <hr /> <div>== SAP Plugin Settings ==<br /> <br /> The SAP Plugin can be used to interact with a SAP system via BAPI.<br /> <br /> === Connection ===<br /> <br /> ==== Java Middleware ====<br /> <br /> The Plugin does use a middleware, the so called Service Client, to communicate with SAP. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\sap\ServiceClient\ServiceClient.jar</div>

Caellwein https://doc.expecco.de/index.php?title=Settings_VisualBasicScriptSettings&diff=5737 2015-12-02T08:51:51Z

<p>Caellwein: Die Seite wurde neu angelegt: „== Visual Basic Script Plugin Settings == The Visual Basic Script Plugin can be used to create, import and execute Visual Basic Script files. This settings d…“</p> <hr /> <div>== Visual Basic Script Plugin Settings ==<br /> <br /> The Visual Basic Script Plugin can be used to create, import and execute Visual Basic Script files.<br /> <br /> This settings dialog is only shown/enabled if the plugin is loaded and licenced. <br /> <br /> === Settings ===<br /> <br /> ==== Scope ====<br /> <br /> To import Visual Basic Script Files the plugin does have a file browser. Using this scope the view of this file browser can be limited to a specific path.<br /> <br /> ==== Delete External Files ====<br /> <br /> If this checkbox is checked files from the file system can be deleted from the Visual Basic Script Plugin file browser.<br /> <br /> === Connection ===<br /> <br /> ==== Script Client ====<br /> <br /> The Plugin does use a middleware, the so called Script Client, to read and execute Script Files. This middleware can run local, as by default, or on a remote connection. If the middleweare does run local the client is started automatically. To do so the path to the client is needed.<br /> <br /> The default path is:<br /> plugin\vbScript\ScriptClient\ScriptClient.exe</div>

Caellwein https://doc.expecco.de/index.php?title=Kategorie:Settings&diff=5736 2015-12-02T08:40:39Z

<p>Caellwein: </p> <hr /> <div>* [[ Settings LanguageSettings]]<br /> * [[ Settings PrinterSettings]]<br /> * [[ Settings LookAndFeelSettings]]<br /> ** [[ Settings TreeSettings]]<br /> ** [[ Settings CodeEditorSettings]]<br /> *** [[ Settings SyntaxColorSettings]]<br /> ** [[ Settings WorksheetEditorSettings]]<br /> *** [[ Settings GeneralWorksheetEditorLookSettings]]<br /> *** [[ Settings WorksheetEditorElementLookSettings]]<br /> ** [[ TableDrivenBlock Settings]]<br /> ** [[ Settings TagColorSettings]]<br /> ** [[ Settings TagIconSettings]]<br /> ** [[ Settings StateColorSettings]]<br /> ** [[ Settings SoundSettings]]<br /> ** [[ Settings FontSettings]]<br /> ** [[ Settings HotKeySettings]]<br /> ** [[ Settings MiscLookSettings]]<br /> * [[ Settings ProjectManagementSettings]]<br /> ** [[ Settings ExpeccoNETSettings]]<br /> * [[ Settings ExecutionSettings]]<br /> ** [[ Settings LoggingSettings]]<br /> ** [[ Settings DebuggerSettings]]<br /> * [[ Settings ReportSettings]]<br /> ** [[ Settings StandardReportTemplateSettings]]<br /> ** [[ Settings CompanySettings]]<br /> * [[ Settings ExternalToolsSettings]]<br /> * [[ Settings UpdatesSettings]]<br /> * [[ Settings PluginSettings]]<br /> ** [[ Settings AndroidGUITestPluginSettings]]<br /> ** [[ Settings CommonJavaGUITestPluginSettings]]<br /> ** [[ Settings GUITestPlatformSettings]]<br /> ** [[ Settings GembirdPluginSettings]]<br /> ** [[ Settings JavaBridgePluginSettings]]<br /> ** [[ Settings ManualTestImport1PluginSettings]]<br /> ** [[ Settings ManualTestImport2PluginSettings]]<br /> ** [[ Settings SAPPluginSettings]]<br /> ** [[ Settings SeleniumPluginSettings]]<br /> ** [[ Settings VisualBasicScriptSettings]]<br /> ** [[ Settings WindowsAutomationPluginSettings]]<br /> ** [[ Settings XMImportPluginSettings]]<br /> * [[ Settings LicenseInstallation]]</div>

Caellwein https://doc.expecco.de/index.php?title=SAP_Testing&diff=5735 2015-11-25T13:27:09Z

<p>Caellwein: /* SAP GUI for Windows */</p> <hr /> <div>=Einführung=<br /> [[Bild:SAP.png|thumb|220px|Architektur der Anbindung]]<br /> expecco kann über unterschiedliche Plug-Ins an SAP-Systeme angebunden werden.<br /> <br /> Die Anbindungen unterscheiden sich logisch und funktional in zwei unterschiedliche Kagegorien, zum einen die Anbindung an die GUI, zum andern die Anbindung an den Anwendungsserver des Systems.<br /> <br /> =Anbindungen an die GUI=<br /> Im folgenden sind unterschiedliche Arten der Anbindung an das SAP-System nach den GUI-Technologien kategorisiert die sie automatisieren.<br /> <br /> == SAP GUI for Windows ==<br /> [[Bild:SAP_GuiScripting.png|thumb|220px|Recording-Tool im SAP-System]]<br /> Das extended Computer Aided Test Tool (eCATT) ist die SAP hauseigene Lösung für die Durchführung von Systemtests in SAP-Systemen und wurde mit Basisrelease 6.20 eingeführt. SAP GUI Scripting ist Teil von eCATT und ermöglicht das Aufzeichnen und Abspielen von Makro-ähnlichen Skripten in Visual Basic Script (VBScript).<br /> <br /> Bei Testszenarien in denen die technologischen Grenzen von SAP-Systemen überschritten werden stößt eCATT allerdings an seine<br /> Grenzen. Hier verweist SAP im SAP Help Portal [http://help.sap.com/saphelp_nw73ehp1/helpdata/DE/49/6d2fa0e0221ec6e10000000a42189b/content.htm?frameset=/de/49/6d3ae6e0221ec6e10000000a42189b/frameset.htm] selbst auf Software von Drittherstellern.<br /> <br /> <br /> Mit Hilfe des [[VBScript|VBScript-Plug-Ins]] können per SAP GUI Scripting aufgenommene VBSRecordings oder manuell erstellten VBScript-Files importiert und parametrisiert werden. In Kombination mit expecco als technologieübergreifende Testumgebung bietet SAP GUI Scripting nahezu ungebrenzte Möglichkeiten.<br /> <br /> Die Anbindung über VBScript-Files und eCATT bietet sich vor allem für eine schnelle Intergation an. Für komplexere und aufwändige Textfälle empfiehlt es sich die Anbindung über die SAP GUI for JAVA in Betracht zu ziehen, da zu späterem Zeitpunkt Anpassungen an den Testfällen auf abstrahierter Ebene vorgenommen werden können.<br /> <br /> == SAP GUI for JAVA ==<br /> Die SAP GUI for Java ist eine SAP-Oberfläche die den plattformunabhängigen Einsatz der SAP-Umgebung ermöglicht. Umgesetzt ist die SAP GUI for Java in Swing, einer frei verfügbaren Grafikbibliothek für die Programmiersprache Java.<br /> <br /> expecco verfügt mittels [[Java Swing GUI Access Library and Plugin|JavaSwing-Plug-In]] über die Fähigkeit Swing-Oberflächen einzubinden. Auf diese Weise kann der Baum der Oberflächenelemente in der Swing-GUI angezeigt und die Interaktion mit der Oberfläche über die zugehörigen Bibliothek automatisiert werden.<br /> <br /> == SAP GUI for HTML ==<br /> Die SAP GUI for HTML ist die SAP-Oberfläche für den Web-Browser. Wie der Name andeutet ist die Implementierung in Hypertext Markup Language (HTML) und JavaScript umgesetzt.<br /> <br /> Zur Anbindung an Web-Technologien existiert für expecco das [[Selenium_Web_Test_Plugin]].<br /> <br /> =Anbindungen an den Server=<br /> Um über die GUI End-to-End-Tests zu realisieren und die Anbindung an Fremdsysteme zu testen werden zusätzlich zur Oberfläche auch funktionale Schnittstellen des SAPSystems an expecco angebunden.<br /> <br /> == BAPI ==<br /> Das Business Application Programming Interface (BAPI) ist eine Schnittstelle in SAPSystemen für den Zugriff auf betriebswirtschaftlichem Abstraktionsniveau. Die BAPI wird im SAP-System selbst aufgerufen, kann aber auch von externen Komponenten getriggert werden.<br /> <br /> Die [[SAP BAPI|SAP BAPI Library]] erlaubt den Zugriff auf die BAPI aus expecco heraus.<br /> <br /> == Webservice ==<br /> In einem SAP-System können bestehende Funktionalitäten nach außen hin als Webservice zur Verfügung gestellt werden. Der per WSDL beschriebene Webservice ist, sofern freigegeben, für Drittsystemen nutzbar. [http://help.sap.com/saphelp_nwpi711/helpdata/de/48/d185ca45885c97e10000000a42189d/content.htm]<br /> <br /> Um Webservices in expecco zu integrieren steht ein [[Calling Webservices via SOAP, XML-RPC or REST|Plug-In]] zur Verfügung.<br /> <br /> [[Category:Plugins]]</div>

Caellwein https://doc.expecco.de/index.php?title=SAP_Testing&diff=5734 2015-11-25T13:26:19Z

<p>Caellwein: /* SAP GUI for Windows */</p> <hr /> <div>=Einführung=<br /> [[Bild:SAP.png|thumb|220px|Architektur der Anbindung]]<br /> expecco kann über unterschiedliche Plug-Ins an SAP-Systeme angebunden werden.<br /> <br /> Die Anbindungen unterscheiden sich logisch und funktional in zwei unterschiedliche Kagegorien, zum einen die Anbindung an die GUI, zum andern die Anbindung an den Anwendungsserver des Systems.<br /> <br /> =Anbindungen an die GUI=<br /> Im folgenden sind unterschiedliche Arten der Anbindung an das SAP-System nach den GUI-Technologien kategorisiert die sie automatisieren.<br /> <br /> == SAP GUI for Windows ==<br /> [[Bild:SAP_GuiScripting.png|thumb|220px|Recording-Tool im SAP-System]]<br /> Das extended Computer Aided Test Tool (eCATT) ist die SAP hauseigene Lösung für die Durchführung von Systemtests in SAP-Systemen und wurde mit Basisrelease 6.20 eingeführt. SAP GUI Scripting ist Teil von eCATT und ermöglicht das Aufzeichnen und Abspielen von Makro-ähnlichen Skripten in Visual Basic Script (VBScript).<br /> <br /> Bei Testszenarien in denen die technologischen Grenzen von SAP-Systemen überschritten werden stößt eCATT allerdings an seine<br /> Grenzen. Hier verweist SAP im SAP Help Portal [http://help.sap.com/saphelp_nw73ehp1/helpdata/DE/49/6d2fa0e0221ec6e10000000a42189b/content.htm?frameset=/de/49/6d3ae6e0221ec6e10000000a42189b/frameset.htm] selbst auf Software von Drittherstellern.<br /> <br /> <br /> Mit Hilfe des [[VBScript|VBScript-Plug-Ins]] können per SAP GUI Scripting aufgenommene VBSRecordings oder manuell erstellten VBScript-Files importiert und parametrisiert werden. In Kombination mit expecco als technologieübergreifende Testumgebung bietet SAP GUI Scripting nahezu ungebrenzte Möglichkeiten.<br /> <br /> Die Anbindung über VBScript-Files und eCATT bietet sich vor allem für eine schnelle Intergation an. Für komplexere und aufwändige Textfälle empfiehlt es sich die Anbindung über die SAP GUI for JAVA in Betracht zu ziehen, da zu späterem Zeitpunkt anpassungen auf abstrahierter Ebene vorgenommen werden können.<br /> <br /> == SAP GUI for JAVA ==<br /> Die SAP GUI for Java ist eine SAP-Oberfläche die den plattformunabhängigen Einsatz der SAP-Umgebung ermöglicht. Umgesetzt ist die SAP GUI for Java in Swing, einer frei verfügbaren Grafikbibliothek für die Programmiersprache Java.<br /> <br /> expecco verfügt mittels [[Java Swing GUI Access Library and Plugin|JavaSwing-Plug-In]] über die Fähigkeit Swing-Oberflächen einzubinden. Auf diese Weise kann der Baum der Oberflächenelemente in der Swing-GUI angezeigt und die Interaktion mit der Oberfläche über die zugehörigen Bibliothek automatisiert werden.<br /> <br /> == SAP GUI for HTML ==<br /> Die SAP GUI for HTML ist die SAP-Oberfläche für den Web-Browser. Wie der Name andeutet ist die Implementierung in Hypertext Markup Language (HTML) und JavaScript umgesetzt.<br /> <br /> Zur Anbindung an Web-Technologien existiert für expecco das [[Selenium_Web_Test_Plugin]].<br /> <br /> =Anbindungen an den Server=<br /> Um über die GUI End-to-End-Tests zu realisieren und die Anbindung an Fremdsysteme zu testen werden zusätzlich zur Oberfläche auch funktionale Schnittstellen des SAPSystems an expecco angebunden.<br /> <br /> == BAPI ==<br /> Das Business Application Programming Interface (BAPI) ist eine Schnittstelle in SAPSystemen für den Zugriff auf betriebswirtschaftlichem Abstraktionsniveau. Die BAPI wird im SAP-System selbst aufgerufen, kann aber auch von externen Komponenten getriggert werden.<br /> <br /> Die [[SAP BAPI|SAP BAPI Library]] erlaubt den Zugriff auf die BAPI aus expecco heraus.<br /> <br /> == Webservice ==<br /> In einem SAP-System können bestehende Funktionalitäten nach außen hin als Webservice zur Verfügung gestellt werden. Der per WSDL beschriebene Webservice ist, sofern freigegeben, für Drittsystemen nutzbar. [http://help.sap.com/saphelp_nwpi711/helpdata/de/48/d185ca45885c97e10000000a42189d/content.htm]<br /> <br /> Um Webservices in expecco zu integrieren steht ein [[Calling Webservices via SOAP, XML-RPC or REST|Plug-In]] zur Verfügung.<br /> <br /> [[Category:Plugins]]</div>

Caellwein https://doc.expecco.de/index.php?title=SAP_Testing&diff=5733 2015-11-25T13:25:56Z

<p>Caellwein: /* SAP GUI for Windows */</p> <hr /> <div>=Einführung=<br /> [[Bild:SAP.png|thumb|220px|Architektur der Anbindung]]<br /> expecco kann über unterschiedliche Plug-Ins an SAP-Systeme angebunden werden.<br /> <br /> Die Anbindungen unterscheiden sich logisch und funktional in zwei unterschiedliche Kagegorien, zum einen die Anbindung an die GUI, zum andern die Anbindung an den Anwendungsserver des Systems.<br /> <br /> =Anbindungen an die GUI=<br /> Im folgenden sind unterschiedliche Arten der Anbindung an das SAP-System nach den GUI-Technologien kategorisiert die sie automatisieren.<br /> <br /> == SAP GUI for Windows ==<br /> [[Bild:SAP_GuiScripting.png|thumb|220px|Recording-Tool im SAP-System]]<br /> Das extended Computer Aided Test Tool (eCATT) ist die SAP hauseigene Lösung für die Durchführung von Systemtests in SAP-Systemen und wurde mit Basisrelease 6.20 eingeführt. SAP GUI Scripting ist Teil von eCATT und ermöglicht das Aufzeichnen und Abspielen von Makro-ähnlichen Skripten in Visual Basic Script (VBScript).<br /> <br /> Bei Testszenarien in denen die technologischen Grenzen von SAP-Systemen überschritten werden stößt eCATT allerdings an seine<br /> Grenzen. Hier verweist SAP im SAP Help Portal [http://help.sap.com/saphelp_nw73ehp1/helpdata/DE/49/6d2fa0e0221ec6e10000000a42189b/content.htm?frameset=/de/49/6d3ae6e0221ec6e10000000a42189b/frameset.htm] selbst auf Software von Drittherstellern.<br /> <br /> <br /> Mit Hilfe des [[VBScript|VBScript-Plug-Ins]] können per SAP GUI Scripting aufgenommene VBSRecordings oder manuell erstellten VBScript-Files importiert und parametrisiert werden. In Kombination mit expecco als technologieübergreifende Testumgebung bietet SAP GUI Scripting nahezu ungebrenzte Möglichkeiten.<br /> <br /> Die Anbindung über VBScript-Files und eCATT bietet sich vor allem für eine schnelle Intergation an. Für komplexere und aufwändige Textfälle empfiehlt es sich die Anbindung über die JAVA in Betracht zu ziehen, da zu späterem Zeitpunkt anpassungen auf abstrahierter Ebene vorgenommen werden können.<br /> <br /> == SAP GUI for JAVA ==<br /> Die SAP GUI for Java ist eine SAP-Oberfläche die den plattformunabhängigen Einsatz der SAP-Umgebung ermöglicht. Umgesetzt ist die SAP GUI for Java in Swing, einer frei verfügbaren Grafikbibliothek für die Programmiersprache Java.<br /> <br /> expecco verfügt mittels [[Java Swing GUI Access Library and Plugin|JavaSwing-Plug-In]] über die Fähigkeit Swing-Oberflächen einzubinden. Auf diese Weise kann der Baum der Oberflächenelemente in der Swing-GUI angezeigt und die Interaktion mit der Oberfläche über die zugehörigen Bibliothek automatisiert werden.<br /> <br /> == SAP GUI for HTML ==<br /> Die SAP GUI for HTML ist die SAP-Oberfläche für den Web-Browser. Wie der Name andeutet ist die Implementierung in Hypertext Markup Language (HTML) und JavaScript umgesetzt.<br /> <br /> Zur Anbindung an Web-Technologien existiert für expecco das [[Selenium_Web_Test_Plugin]].<br /> <br /> =Anbindungen an den Server=<br /> Um über die GUI End-to-End-Tests zu realisieren und die Anbindung an Fremdsysteme zu testen werden zusätzlich zur Oberfläche auch funktionale Schnittstellen des SAPSystems an expecco angebunden.<br /> <br /> == BAPI ==<br /> Das Business Application Programming Interface (BAPI) ist eine Schnittstelle in SAPSystemen für den Zugriff auf betriebswirtschaftlichem Abstraktionsniveau. Die BAPI wird im SAP-System selbst aufgerufen, kann aber auch von externen Komponenten getriggert werden.<br /> <br /> Die [[SAP BAPI|SAP BAPI Library]] erlaubt den Zugriff auf die BAPI aus expecco heraus.<br /> <br /> == Webservice ==<br /> In einem SAP-System können bestehende Funktionalitäten nach außen hin als Webservice zur Verfügung gestellt werden. Der per WSDL beschriebene Webservice ist, sofern freigegeben, für Drittsystemen nutzbar. [http://help.sap.com/saphelp_nwpi711/helpdata/de/48/d185ca45885c97e10000000a42189d/content.htm]<br /> <br /> Um Webservices in expecco zu integrieren steht ein [[Calling Webservices via SOAP, XML-RPC or REST|Plug-In]] zur Verfügung.<br /> <br /> [[Category:Plugins]]</div>

Caellwein https://doc.expecco.de/index.php?title=SAP_Testing&diff=5732 2015-11-25T13:25:44Z

<p>Caellwein: /* SAP GUI for Windows */</p> <hr /> <div>=Einführung=<br /> [[Bild:SAP.png|thumb|220px|Architektur der Anbindung]]<br /> expecco kann über unterschiedliche Plug-Ins an SAP-Systeme angebunden werden.<br /> <br /> Die Anbindungen unterscheiden sich logisch und funktional in zwei unterschiedliche Kagegorien, zum einen die Anbindung an die GUI, zum andern die Anbindung an den Anwendungsserver des Systems.<br /> <br /> =Anbindungen an die GUI=<br /> Im folgenden sind unterschiedliche Arten der Anbindung an das SAP-System nach den GUI-Technologien kategorisiert die sie automatisieren.<br /> <br /> == SAP GUI for Windows ==<br /> [[Bild:SAP_GuiScripting.png|thumb|220px|Recording-Tool im SAP-System]]<br /> Das extended Computer Aided Test Tool (eCATT) ist die SAP hauseigene Lösung für die Durchführung von Systemtests in SAP-Systemen und wurde mit Basisrelease 6.20 eingeführt. SAP GUI Scripting ist Teil von eCATT und ermöglicht das Aufzeichnen und Abspielen von Makro-ähnlichen Skripten in Visual Basic Script (VBScript).<br /> <br /> Bei Testszenarien in denen die technologischen Grenzen von SAP-Systemen überschritten werden stößt eCATT allerdings an seine<br /> Grenzen. Hier verweist SAP im SAP Help Portal [http://help.sap.com/saphelp_nw73ehp1/helpdata/DE/49/6d2fa0e0221ec6e10000000a42189b/content.htm?frameset=/de/49/6d3ae6e0221ec6e10000000a42189b/frameset.htm] selbst auf Software von Drittherstellern.<br /> <br /> <br /> Mit Hilfe des [[VBScript|VBScript-Plug-Ins]] können per SAP GUI Scripting aufgenommene VBSRecordings oder manuell erstellten VBScript-Files importiert und parametrisiert werden. In Kombination mit expecco als technologieübergreifende Testumgebung bietet SAP GUI Scripting nahezu ungebrenzte Möglichkeiten.<br /> Die Anbindung über VBScript-Files und eCATT bietet sich vor allem für eine schnelle Intergation an. Für komplexere und aufwändige Textfälle empfiehlt es sich die Anbindung über die JAVA in Betracht zu ziehen, da zu späterem Zeitpunkt anpassungen auf abstrahierter Ebene vorgenommen werden können.<br /> <br /> == SAP GUI for JAVA ==<br /> Die SAP GUI for Java ist eine SAP-Oberfläche die den plattformunabhängigen Einsatz der SAP-Umgebung ermöglicht. Umgesetzt ist die SAP GUI for Java in Swing, einer frei verfügbaren Grafikbibliothek für die Programmiersprache Java.<br /> <br /> expecco verfügt mittels [[Java Swing GUI Access Library and Plugin|JavaSwing-Plug-In]] über die Fähigkeit Swing-Oberflächen einzubinden. Auf diese Weise kann der Baum der Oberflächenelemente in der Swing-GUI angezeigt und die Interaktion mit der Oberfläche über die zugehörigen Bibliothek automatisiert werden.<br /> <br /> == SAP GUI for HTML ==<br /> Die SAP GUI for HTML ist die SAP-Oberfläche für den Web-Browser. Wie der Name andeutet ist die Implementierung in Hypertext Markup Language (HTML) und JavaScript umgesetzt.<br /> <br /> Zur Anbindung an Web-Technologien existiert für expecco das [[Selenium_Web_Test_Plugin]].<br /> <br /> =Anbindungen an den Server=<br /> Um über die GUI End-to-End-Tests zu realisieren und die Anbindung an Fremdsysteme zu testen werden zusätzlich zur Oberfläche auch funktionale Schnittstellen des SAPSystems an expecco angebunden.<br /> <br /> == BAPI ==<br /> Das Business Application Programming Interface (BAPI) ist eine Schnittstelle in SAPSystemen für den Zugriff auf betriebswirtschaftlichem Abstraktionsniveau. Die BAPI wird im SAP-System selbst aufgerufen, kann aber auch von externen Komponenten getriggert werden.<br /> <br /> Die [[SAP BAPI|SAP BAPI Library]] erlaubt den Zugriff auf die BAPI aus expecco heraus.<br /> <br /> == Webservice ==<br /> In einem SAP-System können bestehende Funktionalitäten nach außen hin als Webservice zur Verfügung gestellt werden. Der per WSDL beschriebene Webservice ist, sofern freigegeben, für Drittsystemen nutzbar. [http://help.sap.com/saphelp_nwpi711/helpdata/de/48/d185ca45885c97e10000000a42189d/content.htm]<br /> <br /> Um Webservices in expecco zu integrieren steht ein [[Calling Webservices via SOAP, XML-RPC or REST|Plug-In]] zur Verfügung.<br /> <br /> [[Category:Plugins]]</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:Jira_Library.png&diff=5729 2015-11-04T13:39:52Z

<p>Caellwein: Caellwein lud eine neue Version von „Datei:Jira Library.png“ hoch</p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Jira_Plugin_Reference/en&diff=5728 2015-11-04T13:37:38Z

<p>Caellwein: </p> <hr /> <div>[[Bild:Test Case With Jira Issue Id.png|thumb|300px|A test case with a JIRA issue-ID]]<br /> == JIRA Interface Plugin ==<br /> The JIRA plugin allows for test-cases to be linked with an issue within the JIRA issue tracking system. For that, an optional issue-ID can be added to a testCase. Whenever a testcase with an associated Jira issue-ID is executed, the Jira database gets updated.<br /> <br /> After test-execution, the plugin is informed and sends an REST request (updateIssue) to the JIRA service. <br /> <br /> === Settings ===<br /> '''JIRA Server Settings'''<br /> <br /> Before interacting with JIRA using webservices go to the JIRA system settings and ensure Remote-API-Access is ON.<br /> For further information on how to configurate your JIRA server please refere to the [https://confluence.atlassian.com/display/JIRA/JIRA+User%27s+Guide JIRA user guide].<br /> <br /> '''Expecco Settings'''<br /> <br /> Opening Extras &gt; Settings &gt; Pugins &gt; JIRA Interface you can enter the JIRA connection details. If you enter them using the settings instead of the connection dialog itself you don't have to reenter them if you need to reconnect.<br /> <br /> === Connecting to JIRA ===<br /> To connect to JIRA open Pugins &gt; JIRA &gt; Define JIRA Connection and enter the connection details.<br /> <br /> <br /> [[Datei:Jira_Connection.png|500px]]<br /> <br /> <br /> == JIRA Interface Library ==<br /> In addition to the automatic issue update (which is controlled via the user interface and therefore requires no additional programming), a library of building blocks to interact with JIRA is provided. The library is based on REST for communication.<br /> <br /> Of course, the corresponding service endpoint has to be enabled and running on your JIRA server site.<br /> <br /> === JIRA Interface Blocks ===<br /> <br /> [[Datei:Jira_Library.png]]<br /> <br /> === See Also ===<br /> As an alternative of using the JIRA Interface Library, you can also import a webservice description by yourself. <br /> <br /> *[[WSDL Service Import Plugin]]<br /> <br /> &lt;hr&gt;<br /> Back to [[Online_Documentation#Library_and_Plugin_Overview | Online Documentation]].<br /> <br /> [[Category:Plugins]]</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:FindTableSetting.png&diff=5700 2015-10-21T08:46:03Z

<p>Caellwein: Caellwein lud eine neue Version von „Datei:FindTableSetting.png“ hoch</p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Settings_TableDrivenBlock/en&diff=5699 2015-10-21T08:44:34Z

<p>Caellwein: /* Where To Find */</p> <hr /> <div>[[Bild:FindTableSetting.png|thumb|150px|Where to find the settings for table driven tests]]<br /> = Where to Find =<br /> <br /> The settings for the table editor can be found in the expecco settings-tree in the category 'Look &amp; Feel'.<br /> <br /> = Table Editor =<br /> [[Bild:TableSetting.png|thumb|300px|Settings for table driven tests]]<br /> The settings are applied to the table editor of the table driven block:<br /> <br /> *'''Set Default Values for new Steps'''&lt;br&gt; If checked the input pins of new steps will be initialized with default values. &lt;br&gt;<br /> <br /> *'''Expand Compund Step'''&lt;br&gt; Open editor with expanded steps. &lt;br&gt;<br /> <br /> *'''Font'''&lt;br&gt; The font to display the table in. &lt;br&gt;<br /> <br /> === Inputs === <br /> <br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> *'''Adjust Editor to view'''&lt;br&gt; If ckeched the editor will be drawn on the column width. &lt;br&gt;<br /> <br /> *'''Stretch input only'''&lt;br&gt; If checked input pins will be drawn with column width if there is no output pin for the step. &lt;br&gt;<br /> <br /> === Outputs ===<br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> = Look-LogView=<br /> <br /> The settings are applied to the log view of the table driven block:<br /> <br /> *'''Expand Compund Step'''&lt;br&gt; Open editor with expanded steps. &lt;br&gt;<br /> <br /> *'''Font'''&lt;br&gt; The font to display the table in. &lt;br&gt;<br /> <br /> === Inputs === <br /> <br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> *'''Adjust Editor to view'''&lt;br&gt; If ckeched the editor will be drawn on the column width. &lt;br&gt;<br /> <br /> *'''Stretch input only'''&lt;br&gt; If checked input pins will be drawn with column width if there is no output pin for the step. &lt;br&gt;<br /> <br /> === Outputs ===<br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> [[Category:Settings]]</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:FindTableSetting.png&diff=5698 2015-10-21T08:44:01Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Settings_TableDrivenBlock/en&diff=5697 2015-10-21T08:43:50Z

<p>Caellwein: </p> <hr /> <div>[[Bild:FindTableSetting.png|thumb|150px|Where to find the settings for table driven tests]]<br /> = Where To Find =<br /> <br /> The settings for the table editor can be found in the expecco settings-tree in the category 'Look &amp; Feel'.<br /> <br /> = Table Editor =<br /> [[Bild:TableSetting.png|thumb|300px|Settings for table driven tests]]<br /> The settings are applied to the table editor of the table driven block:<br /> <br /> *'''Set Default Values for new Steps'''&lt;br&gt; If checked the input pins of new steps will be initialized with default values. &lt;br&gt;<br /> <br /> *'''Expand Compund Step'''&lt;br&gt; Open editor with expanded steps. &lt;br&gt;<br /> <br /> *'''Font'''&lt;br&gt; The font to display the table in. &lt;br&gt;<br /> <br /> === Inputs === <br /> <br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> *'''Adjust Editor to view'''&lt;br&gt; If ckeched the editor will be drawn on the column width. &lt;br&gt;<br /> <br /> *'''Stretch input only'''&lt;br&gt; If checked input pins will be drawn with column width if there is no output pin for the step. &lt;br&gt;<br /> <br /> === Outputs ===<br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> = Look-LogView=<br /> <br /> The settings are applied to the log view of the table driven block:<br /> <br /> *'''Expand Compund Step'''&lt;br&gt; Open editor with expanded steps. &lt;br&gt;<br /> <br /> *'''Font'''&lt;br&gt; The font to display the table in. &lt;br&gt;<br /> <br /> === Inputs === <br /> <br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> *'''Adjust Editor to view'''&lt;br&gt; If ckeched the editor will be drawn on the column width. &lt;br&gt;<br /> <br /> *'''Stretch input only'''&lt;br&gt; If checked input pins will be drawn with column width if there is no output pin for the step. &lt;br&gt;<br /> <br /> === Outputs ===<br /> *'''Columns Width'''&lt;br&gt; The width (min) of the column. &lt;br&gt;<br /> <br /> *'''Colums Width is fixed'''&lt;br&gt; If checked the column width is fixed and will not be ajusted to the window size. &lt;br&gt;<br /> <br /> [[Category:Settings]]</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5680 2015-10-13T09:17:50Z

<p>Caellwein: /* Common Options (Context Menu) */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto...'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto...'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to edit the freeze value of the selected pin.<br /> <br /> *'''Add and Remove Pin'''&lt;br&gt;Add or remove a pin, if possible.<br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5679 2015-10-13T09:17:41Z

<p>Caellwein: /* Step Specific Options (Context Menu) */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto...'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to edit the freeze value of the selected pin.<br /> <br /> *'''Add and Remove Pin'''&lt;br&gt;Add or remove a pin, if possible.<br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5678 2015-10-13T08:27:12Z

<p>Caellwein: /* Pin Specific Options (Context Menu) */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to edit the freeze value of the selected pin.<br /> <br /> *'''Add and Remove Pin'''&lt;br&gt;Add or remove a pin, if possible.<br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5677 2015-10-13T08:26:16Z

<p>Caellwein: /* Pin Specific Options (Context Menu) */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add and Remove Pin'''&lt;br&gt;Add or remove a pin, if possible.<br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5676 2015-10-13T08:26:01Z

<p>Caellwein: /* Pin Specific Options (Context Menu) */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add and Remove Pin'''&lt;br&gt;Add or remove a pin if possible.<br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:Context_Pin_Menu.png&diff=5675 2015-10-13T08:23:41Z

<p>Caellwein: Caellwein lud eine neue Version von „Datei:Context Pin Menu.PNG“ hoch</p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Datei:Main_Menu.png&diff=5674 2015-10-13T08:20:03Z

<p>Caellwein: Caellwein lud eine neue Version von „Datei:Main Menu.PNG“ hoch</p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5673 2015-10-13T08:18:40Z

<p>Caellwein: /* Main Menu */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to. <br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step. <br /> <br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:Main_Menu.png&diff=5672 2015-10-13T08:18:09Z

<p>Caellwein: Caellwein lud eine neue Version von „Datei:Main Menu.PNG“ hoch</p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Datei:BreakWithSuccessLineIndicator.png&diff=5671 2015-10-13T08:09:43Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5670 2015-10-13T08:09:31Z

<p>Caellwein: /* Indicators */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessLineIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Convert the table driven block to a compound block or copy as compound to clipboard.<br /> <br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to. <br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step. <br /> <br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:WriteToOutput.png&diff=5669 2015-10-13T08:06:45Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Datei:WriteToEnvironment.png&diff=5668 2015-10-13T08:06:29Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Datei:ValueMustBeEqualTo.png&diff=5667 2015-10-13T08:04:02Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Datei:ValueMayNOTBeEqualTo.png&diff=5666 2015-10-13T08:03:50Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=Datei:Inconclusive.png&diff=5665 2015-10-13T08:03:29Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5664 2015-10-13T08:03:18Z

<p>Caellwein: /* Compare Pin Value */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Convert the table driven block to a compound block or copy as compound to clipboard.<br /> <br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to. <br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step. <br /> <br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=Datei:BreakWithFailureIndicator.png&diff=5663 2015-10-13T08:02:43Z

<p>Caellwein: </p> <hr /> <div></div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5662 2015-10-13T07:57:57Z

<p>Caellwein: /* Compare Pin Value */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakPointed.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Convert the table driven block to a compound block or copy as compound to clipboard.<br /> <br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to. <br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step. <br /> <br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5661 2015-10-13T07:57:25Z

<p>Caellwein: /* Compare Pin Value */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailureIndicator.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Convert the table driven block to a compound block or copy as compound to clipboard.<br /> <br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to. <br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step. <br /> <br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein https://doc.expecco.de/index.php?title=TableDrivenBlock_Editor-Table_Editor/en&diff=5660 2015-10-13T07:56:07Z

<p>Caellwein: /* Compare Pin Value */</p> <hr /> <div>[[Bild:TableDrivenEditor.png|thumb|300px|Table driven test editor]]<br /> <br /> <br /> The following document describes the table driven test editor used to view and edit [[TableDrivenBlock Element |table driven blocks]]. The table driven test editor can be used for tests with a sequential test flow. <br /> <br /> If tests get more complex table driven blocks can be transformed to compound blocks as described [[#Main_Menu|here]]. <br /> <br /> == Toolbar ==<br /> [[Bild:Table Driven Editor Toolbar.png]]<br /> <br /> The toolbar area consists of two different groups.<br /> In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.<br /> &lt;br&gt;&lt;br&gt;<br /> *[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named &quot;Test/Demo&quot; (which is the rightmost tab of the editor).<br /> &lt;br&gt;<br /> *[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.<br /> &lt;br&gt;<br /> *[[Bild:Icon_Expand.png]] Expand all step items; all In- and Outpur pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.<br /> <br /> == Tasks ==<br /> <br /> === Adding Steps ===<br /> There are three possibilities to add new entries so called steps to the table:<br /> * via drag &amp; drop from the project tree<br /> * by using the conext menu entry 'New Step'<br /> * or by copy &amp; paste step from a table or network.<br /> <br /> The step is initially selected, indicated by the highlited row.&lt;br&gt;<br /> The inputs of the new created steps are set to its default value dependent on the [[ TableDrivenBlock_Settings/en |settings]] or if copied the values are adapted from the copied step.<br /> <br /> === Selecting Steps ===<br /> Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.<br /> <br /> Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.<br /> <br /> === Arranging Steps === <br /> To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.<br /> <br /> === Supplying Steps with Values ===<br /> There are three different ways to set a value for a certain step:<br /> <br /> *[[Bild:ReadFromFreezeValue.png]] Values can be set directly and be 'frozen' to the pin.<br /> <br /> *[[Bild:ReadFromEnvironment.png]] Values can be read from environment variables. If the environment contains a variable whose datatype is matching the pins datatype the variable will be suggested.<br /> <br /> *[[Bild:ReadFromPin.png]] Values can be read from input pins. If the block description contains a pin whose datatype is matching the pins datatype the pin will be suggested.<br /> <br /> == Output Pin Operations ==<br /> === Compare Pin Value ===<br /> The following operations can be used to ensure a specific value at this pin: <br /> <br /> *[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''&lt;br&gt; The value at this pin must be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''&lt;br&gt; The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.<br /> <br /> *[[Bild:BreakWithSuccess.png]] '''Break with success'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with success.<br /> <br /> *[[Bild:BreakWithFailure.png]] '''Failed'''&lt;br&gt; If this pin is triggered the execution of the table driven block will break with a failure.<br /> <br /> *[[Bild:Inconclusive.png]] '''Inconclusive'''&lt;br&gt; If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.<br /> &lt;br&gt;<br /> <br /> === Save Pin Value ===<br /> The following operations can be used to make the value, available at this pin, accessible: <br /> <br /> *[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''&lt;br&gt; Write the value to a environment variable to further use.<br /> <br /> *[[Bild:WriteToOutput.png]] '''Write to Output'''&lt;br&gt; Write the value to the table driven blocks output pin. The value can be accessed in the sequenze the block is executed in, but not be accessed in the table driven block itself.<br /> &lt;br&gt;<br /> <br /> == Indicators ==<br /> *[[Bild:BreakWithSuccessIndicator.png]] The stap has a break with success set at a output pin. When the output pin is triggered the execution of the table is aborted with success as return value.<br /> <br /> *[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the &quot;Run/Continue&quot; or the &quot;Single-Step&quot; button tp be pressed.<br /> &lt;br&gt;<br /> <br /> == Menu ==<br /> <br /> === Main Menu ===<br /> [[Bild:Main Menu.PNG|thumb|250px|Main Menu Options]]<br /> This menu can be found as 'Diagram' in the main menu:<br /> &lt;br&gt;<br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Convert the table driven block to a compound block or copy as compound to clipboard.<br /> <br /> *'''Import from CSV file ...'''&lt;br&gt;Add new steps and freeze the values from the imported csv file to the input pins.<br /> <br /> *'''Environment...'''&lt;br&gt;Open an dialog to inspect the tables environment.<br /> &lt;br&gt;<br /> <br /> === Common Options (Context Menu) === <br /> [[Bild:Context Menu.PNG|thumb|250px|Common Options]]<br /> When nothing is selected in the editor:<br /> &lt;br&gt;<br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching item.<br /> <br /> *'''Aspect'''&lt;br&gt;Expand or collapse all steps.<br /> &lt;br&gt;<br /> <br /> === Step Specific Options (Context Menu) === <br /> [[Bild:Context Step Menu.PNG|thumb|250px|Step Specific Options]]<br /> When a step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Copy, Paste and Delete'''&lt;br&gt;Copy and delete the selected step or insert after selected step.<br /> <br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Add Extra Page on Selected Item'''&lt;br&gt;Open a extra page on the selected step to inspect the steps functionality.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to.<br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step.<br /> <br /> *'''New Step'''&lt;br&gt;Add a new step item to the table.<br /> <br /> *'''Replace By'''&lt;br&gt;Replace the selected item by a new step item.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected step in the indicared direction within the table.<br /> <br /> *'''Toggle Breakpoint'''&lt;br&gt;Toggle a breakpoint on the selected step.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected step.<br /> &lt;br&gt;<br /> <br /> === Multiple Step Specific Options (Context Menu) === <br /> [[Bild:Context Multiple Step Menu.PNG|thumb|250px|Multiple Step Specific Options]]<br /> When more than one step is selected in the editor:<br /> &lt;br&gt;<br /> *'''Delete'''&lt;br&gt;Delete the selected steps.<br /> <br /> *'''Move Up and Move Down'''&lt;br&gt;Move the selected steps in the indicared direction within the table.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins.<br /> <br /> *'''Properties...'''&lt;br&gt;Open a dialog to change the background of the selected steps.<br /> <br /> *'''Aspect'''&lt;br&gt;Contains menu entries to expand or collapse all steps.<br /> <br /> *'''Refactor'''&lt;br&gt;Extract, or extract and replace selected steps with, a new table with a copy of the selected steps.<br /> &lt;br&gt;<br /> <br /> === Pin Specific Options (Context Menu) === <br /> [[Bild:Context Pin Menu.PNG|thumb|250px|Pin Specific Options]]<br /> When a pin is selected in the editor:<br /> &lt;br&gt;<br /> *'''Open Editor'''&lt;br&gt;Open an editor to rename the selected step.<br /> <br /> *'''Goto'''&lt;br&gt;Open an dialog to ask for a step number to go to. <br /> <br /> *'''Find, Find Next and Find Previous'''&lt;br&gt;Open the search function and find the next or previous matching step. <br /> <br /> *'''Move Variable To'''&lt;br&gt;Move a value, dedicated to the steps pin, to the table's pin or environment.<br /> <br /> *'''Freeze and Unfreeze'''&lt;br&gt;Freeze or unfreeze default values to the pins. <br /> &lt;br&gt;<br /> <br /> == Settings ==<br /> Aspect and behavour of a table driven block can be affected via the [[TableDrivenBlock_Settings/en | Settings Dialog]].</div>

Caellwein