Tutorials/en: Unterschied zwischen den Versionen

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen
 
(42 dazwischenliegende Versionen von 4 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
<br>
= First steps expecco =

= First Steps with expecco =


The first steps are directed to all who are using expecco for the first time and for the first help. With a simple example we give an overview of expecco. It is recommended to start expecco parallel to the tutorial to be able to follow all steps within expecco.
The first steps are directed to all who are using expecco for the first time and for the first help. With a simple example we give an overview of expecco. It is recommended to start expecco parallel to the tutorial to be able to follow all steps within expecco.


[[Medium:Erste_Schritte_mit_expecco.pdf|Erste Schritte mit expecco.pdf]]
[[Medium:Expecco_-_Quick_Start_Guide.pdf|expecco Quick Start Guide.pdf]]


= First steps with Android =
= First Steps with Web Test =
* [[Web Test Tutorial - Part 1]]
* [[Web Test Tutorial - Part 2]]


= First Steps with Mobile Devices =
The Mobile Testing Plugin can be used to create and run tests for apps on Android or iOS mobile devices. This tutorial describes the basic procedure using an example for Android, consisting of a simple app and an expecco test suite. The expecco Mobile Demo app calculates and checks various everyday codes: the IBAN from European payment transactions, the international GTIN-13 product codes, how to find them in retail barcodes, and the serial numbers on euro banknotes. The test-suite contains test cases for individual functions of the app. During the tutorial we will show you how to develop missing functions.


The Mobile Testing Plugin is used to create and run tests for apps on Android or iOS mobile devices. This tutorial describes the basic procedure using an example for Android and iOS, consisting of a simple app and an expecco test suite. The expecco Mobile Demo app calculates and checks various everyday codes: the IBAN from European payment transactions, the international GTIN-13 product codes, how to find them in retail barcodes, and the serial numbers on euro banknotes. The test-suite contains test cases for individual functions of the app. During the tutorial we will show you how to develop missing functions.
'''"Erste Schritte mit Android" als pdf:'''


You find the tutorial on the page [[Mobile_Testing_Tutorial/en|Mobile Testing Tutorial]] in two versions for Android and iOS devices.
[[Medium:Erste_Schritte_mit_Android.pdf|Erste Schritte mit Android.pdf]]
* [[Mobile_Testing_Tutorial/en#First_steps_with_Android|First steps with Android]]
* [[Mobile_Testing_Tutorial/en#First_steps_with_iOS|First steps with iOS]]


<!--'''"Erste Schritte mit mobile devices" als pdf:'''

[[Medium:Erste_Schritte_mit_Android.pdf|Erste Schritte mit mobile devices.pdf]]-->
'''Tutorial als Video bei "YouTube":'''
'''Tutorial als Video bei "YouTube":'''


[https://www.youtube.com/watch?v=H8H4gQO_Tx8 Testing with Android]
[https://www.youtube.com/watch?v=H8H4gQO_Tx8 Testing with mobile devices]


= First Steps with Web Test =
= First Steps Manual Tests =
* [[Web Test Tutorial]]
* [[Web Test Tutorial Part 2]]


This tutorial given an introduction how to create guided manual tests with expecco.
= Function Libraries =
Manual tests can also be imported from spezifications (excel and other documents), and later incrementally in part or whole automated.


*[[Manual Test Tutorial/en | Manual Test Tutorial]]
'''Video "Verwendung von Bibliotheken" bei "YouTube":'''- currently only available in German language


= First Steps OPCUA=
[https://www.youtube.com/watch?v=moi3AiexalQ Verwendung von Bibliotheken]


*[[OPC/en|Short Description of the OPC Library]]
<br>
Video tutorial: [[Datei:OPCUATutorial.mp4|OPCUATutorial.mp4]]


= [[Setting up an HTTP-Server/en | Tutorial: Setting up an HTTP-Server]] =
= Generieren von Testdaten =


This document demonstrates how to quickly setup an HTTP-server using standard actions. This can respond with dynamically generated answers.
One of the most frequently asked questions is "How can I generate testdata". Due to expecco's flexibility, there are multiple solutions to solving this task. Depending on the kind and amount of data to be generated, one of several patterns applies. The following gives you a rough overview on that theme.


= Function Libraries =
'''Hier können Sie "Generieren von Testdaten" nutzen:'''


'''Video "expecco`s Function Libraries" bei "YouTube":'''- currently only available in german language
[[Generating Test Data|Tutorial: Generieren von Testdaten]]


[https://www.youtube.com/watch?v=moi3AiexalQ Verwendung von Bibliotheken]
= Der Umgang mit Bausteinen =


= [[Generating Test Data|Tutorial: How to Generate Test Data]] =
'''Video "Umgang mit Bausteinen bei "YouTube":'''


One of the most frequently asked questions is "How can I generate testdata". Due to expecco's flexibility, there are multiple solutions to solving this task. Depending on the kind and amount of data to be generated, one of several patterns applies. The following gives you a rough overview on that theme.
[https://www.youtube.com/watch?v=GYXXyJWmNT8 Umgang mit Bausteinen]


= Working with Action Blocks =
<br>


Sorry, the YouTube video "''Working with Action Blocks''" is currently only available in German.
= Weitere Tutorials =
<br>[https://www.youtube.com/watch?v=GYXXyJWmNT8 Umgang mit Bausteinen]


* [[Testing Java Applications using Groovy blocks]]
= [[Testing Java Applications using Groovy blocks]] =
Through this tutorial, we'll use a simple "Bank Account" application as system under test.
Through this tutorial, we'll use a simple "Bank Account" application as system under test.


= [[expecco API]] =
<br>

* [[expecco API]]
Before you start programming, please read the [[How_to_Program/en|"How to Program"]] document, which describes how program code is handled in expecco.
Before you start programming, please read the [[How_to_Program/en|"How to Program"]] document, which describes how program code is handled in expecco.
Unless you are familiar with the dynamics of a Smalltalk development environment, some of it may be unknown to you, and you will have more fun and be more productive, if you know the power of the tools. For the best development experience, take a look at the debugger, workspace (notepad) and data inspectors.
Unless you are familiar with the dynamics of a Smalltalk development environment, some of it may be unknown to you, and you will have more fun and be more productive, if you know the power of the tools. For the best development experience, take a look at the debugger, workspace (notepad) and data inspectors.
Zeile 58: Zeile 66:
The rest of this document describes the syntax and semantics of the elementary action languages; for tool usage, please read the [[How_to_Program/en|HowTo]] document.
The rest of this document describes the syntax and semantics of the elementary action languages; for tool usage, please read the [[How_to_Program/en|HowTo]] document.


= [[Parametrizing Tests|Parametrizing Tests]] =
<br>
Parameter values (like hostnames, port numbers, user names, DB names, UI-Element locators etc.) should usually not be used literally as freeze value or hard coded into an elementary block's code, because this may make the suite harder to maintain in that you'd have to search for such values whenever a change is required (using the string search facility in the left tree view).


Instead, either fetch them from an attached file (for example, using the CSV reader), or create an environment variable and fetch the value from there.
* [[Parametrizing Tests|Parametrisierung von Tests]]
Be reminded, that the top-level variables can be initialized from a parameter file (both via the command line and/or dynamically via the menu or by an action block).
Parameter values (like hostnames, port numbers, user names, DB names etc.) should usually not be used literally as freeze value or hard coded into an elementary block's code, because this may make the suite harder to maintain in that you'd have to search for such values whenever a change is required (using the string search facility in the left tree view).
Thus, you can separate the configuration from the actual suite.


= Organization - Best Practices =
<br>

* [[Common_Errors/en|Common Errors and How to Deal with them]]
This document lists the most common error situations and provides advice on how to fix it. It is incomplete and does not cover all possible errors.

<br>

* [[Executor]]

<br>

* [[Executor#Activity]]

<br>

* [[Reimporting a Library|Reimportieren von Bibliotheken]]

<br>


* [[Best Practices#General Suite Organization|General Suite Organization]]
* [[Uses of Tags|Nutzung von Etiketten (Tags)]]
* [[Best Practices#Use of Libraries|Use of Libraries]]
* [[Best Practices#UI Tests|UI Tests]]

Aktuelle Version vom 11. April 2025, 12:59 Uhr


First Steps with expecco[Bearbeiten]

The first steps are directed to all who are using expecco for the first time and for the first help. With a simple example we give an overview of expecco. It is recommended to start expecco parallel to the tutorial to be able to follow all steps within expecco.

expecco Quick Start Guide.pdf

First Steps with Web Test[Bearbeiten]

First Steps with Mobile Devices[Bearbeiten]

The Mobile Testing Plugin is used to create and run tests for apps on Android or iOS mobile devices. This tutorial describes the basic procedure using an example for Android and iOS, consisting of a simple app and an expecco test suite. The expecco Mobile Demo app calculates and checks various everyday codes: the IBAN from European payment transactions, the international GTIN-13 product codes, how to find them in retail barcodes, and the serial numbers on euro banknotes. The test-suite contains test cases for individual functions of the app. During the tutorial we will show you how to develop missing functions.

You find the tutorial on the page Mobile Testing Tutorial in two versions for Android and iOS devices.

Tutorial als Video bei "YouTube":

Testing with mobile devices

First Steps Manual Tests[Bearbeiten]

This tutorial given an introduction how to create guided manual tests with expecco. Manual tests can also be imported from spezifications (excel and other documents), and later incrementally in part or whole automated.

First Steps OPCUA[Bearbeiten]

Video tutorial: Datei:OPCUATutorial.mp4

Tutorial: Setting up an HTTP-Server[Bearbeiten]

This document demonstrates how to quickly setup an HTTP-server using standard actions. This can respond with dynamically generated answers.

Function Libraries[Bearbeiten]

Video "expecco`s Function Libraries" bei "YouTube":- currently only available in german language

Verwendung von Bibliotheken

Tutorial: How to Generate Test Data[Bearbeiten]

One of the most frequently asked questions is "How can I generate testdata". Due to expecco's flexibility, there are multiple solutions to solving this task. Depending on the kind and amount of data to be generated, one of several patterns applies. The following gives you a rough overview on that theme.

Working with Action Blocks[Bearbeiten]

Sorry, the YouTube video "Working with Action Blocks" is currently only available in German.
Umgang mit Bausteinen

Testing Java Applications using Groovy blocks[Bearbeiten]

Through this tutorial, we'll use a simple "Bank Account" application as system under test.

expecco API[Bearbeiten]

Before you start programming, please read the "How to Program" document, which describes how program code is handled in expecco. Unless you are familiar with the dynamics of a Smalltalk development environment, some of it may be unknown to you, and you will have more fun and be more productive, if you know the power of the tools. For the best development experience, take a look at the debugger, workspace (notepad) and data inspectors.

The rest of this document describes the syntax and semantics of the elementary action languages; for tool usage, please read the HowTo document.

Parametrizing Tests[Bearbeiten]

Parameter values (like hostnames, port numbers, user names, DB names, UI-Element locators etc.) should usually not be used literally as freeze value or hard coded into an elementary block's code, because this may make the suite harder to maintain in that you'd have to search for such values whenever a change is required (using the string search facility in the left tree view).

Instead, either fetch them from an attached file (for example, using the CSV reader), or create an environment variable and fetch the value from there. Be reminded, that the top-level variables can be initialized from a parameter file (both via the command line and/or dynamically via the menu or by an action block). Thus, you can separate the configuration from the actual suite.

Organization - Best Practices[Bearbeiten]



Copyright © 2014-2024 eXept Software AG