You can customize the list of tag in a static way by selecting the tags from the combo.

But you can also define a search text that will be used to dynamicaly retreive the list of tag.

NB : If the list of tag is defined, the search Text will be ignored.

You will find below definitions of Cerberus common terms.

You will find in this section a graphical representation of the main Cerberus elements.

Below the system :

Below the test case :

First steps as an administrator

You will find below setting steps for an application to test.

Technical settings are now finished. Please refer to the following section to implement a TestCase.

First steps

You will find below step to create and execute a TestCase.

Congratulations, you’ve just executed your first Cerberus TestCase !

Something is incorrect/missing in this section? Feel free to submit modification.

The Activation Criterias defines condition to enable/block the Testcase to be launched in specific context (countries, environment…​). This level of specification is the most important (override all the others conditions)

A Test case can be linked to multiple Labels depending on their assigned system (see labels section)

You can define Robot constrains at test case level in order to force the execution a specific test case with a specific UserAgent or ScreenSize. This is used to test some specific behavior of a website for a given UserAgent or ScreenSize. You can tune the list of UserAgent and ScreenSize proposed in autocomplete mode (on the GUI) by modifying the respective public invariant USERAGENT and SCREENSIZE.

UserAgent and ScreenSize will be defined at execution level following the rule :

Your step is created. if you want to put it in library, just click on the book on the right side. A step in library will be available to add it in all test cases of your current system.

In the following screenshot you can see a use step. This step is imported from the previous library step. You are not able to modify it (all fields are grey). But you can find a link at the top to open the library if you want to modify your step. All use steps from this library will be impacted by your modification.

To modify only this use step, you have to click on the padlock icon but it will not be a use step anymore. (modification on library step will not affect it)

Something is incorrect/missing in this section? Feel free to submit modification.

Unknown action. Should be used when the action is not yet known. Warning: make the execution fail.

Click on the left mouse button on an element inside the current page.

Value1 Identifier and name of the element to click in the form of : identifier=html_reference.

Click during a specific duration on the left mouse button on an element inside the current page.

Value1 Identifier and name of the element to click in the form of : identifier=html_reference.

Value2 Duration of the click in milliseconds.

Press and keep the left mouse button pressed on an element until the action 'mouseLeftButtonRelease' is executed. If element not defined, Sikuli engine will be used and mouse button will be pressed on the current pocsition of the mouse pointer.

Value1 Identifier and name of the element to click in the form of : identifier=html_reference.

Release the mouse button on an element. Usefull with ButtonPress to perform drag & drop but also to draw picture using Sikuli engine.

Value1 Identifier and name of the element where release will be done in the form of : identifier=html_reference.

Double click on an element inside the current page.

Value1 Identifier and name of the element to click in the form of : identifier=html_reference.

Right click on an element inside the current page.

Value1 Identifier and name of the element to double click in the form of : identifier=html_reference.

Mouse cursor over an element inside the current page.

Value1 Identifier and name of the element to over in the form of : identifier=html_reference.

Allow to move the mouse.

Value1 List of x and y relative position to move the mouse pointer. Several move positions can be specified separated by semi comma. Top Left position of the screen correspond to 0,0 coords. You can specify absolute coords by using keywork absolute before the coords. center keyword can be used to move pointer to center of the screen.

Set the focus to a specific frame on the current page.

Value1 Identifier and name of the frame to focus in the form of : identifier=html_reference.

Set back the focus to the previous frame on the current page.

Switch the focus to another window (like popup dialog).

Value1 Title or URL of the other window to switch to. identifier=html_reference identifier can be title, url, regexUrl or regexTitle

Switch the current application context to another.

Value1 Name of the context you want to switch to. If the value is empty, this will switch to the default context "NATIVE_APP". For example, you can set this action with defined value to switch on the context you want, then do your actions in this context, and finally set again this action with no value to get back to the default context.

Close the browser popup alert windows either by accepting it with ok either by cancelling it with cancel

Value1 ok or cancel

Keypress inside the browser popup alert windows.

Value1 List of characters to type. You can use several special keys into the same action

OpenUrl action using the base defined in the application / environment section.

Value1 Relative URL to open.

OpenUrl action using the login page defined at application / environment level.

Open a specified full url.

Value1 Complete URL to open.

Reload the current page.

Execute a JS script (no output can be retrieved).

Value1 Javascript to execute.

Execute a Command on the robot side. You can follow the Appium instructions here.

Value1 Command to execute. Ex : mobile:deepLink

Value2 Arguments of the command. Ex : {url: "https://www.site.com/", package: "com.site.SomeAndroidPackage"}

Execute a Command from the Cerberus Server side. The command will be executed using the user defined in the parameter cerberus_executeCerberusCommand_user, password defined in cerberus_executeCerberusCommand_password and script from the path cerberus_executeCerberusCommand_path

Value1 Command to execute.

Open an Application. For GUI and FAT, this action require the Cerberus Sikuli extention.

Value1 Application to Open. BundleId for IPA (activateApp() method is used), if empty, launchApp() method is used). App Package for APK ('am start' command is used).

Value2 App Activity for APK.

Close an application.

Value1 Application to Open.

Will Drag from an Element to another Element.

Value1 Identifier and name of the element to drag in the form of : identifier=html_reference.

Value2 Identifier and name of the element where to drop in the form of : identifier=html_reference..

Select an option in a <select> Element. this 'text' must be defined : <option value="text">. For APK and IPA, action only works in a web mode.

Value1 Identifier and name of the element of the select in the form of : identifier=html_reference.

Value2 Element to select.

will allow you to press any key in the current page. Value3 contains the modifier that can be used.

Value1 : Identifier and name of the element where the key is pressed in the form of : identifier=html_reference.

Value2 : Keycode of the key to press.

Value3 : Keycode of the modifier key to press at the same time of the Value2 key pressed.

The keycodes (see. keypress action) also changes depending on the application type (GUI, IPA, APK or FAT). The syntaxes are:

Following Selenium KEYNAME can be used : NULL, CANCEL, HELP, BACK_SPACE, TAB, CLEAR, RETURN, ENTER, SHIFT, LEFT_SHIFT, CONTROL, LEFT_CONTROL, ALT, LEFT_ALT, PAUSE, ESCAPE, SPACE, PAGE_UP, PAGE_DOWN, END, HOME, LEFT, ARROW_LEFT, UP, ARROW_UP, RIGHT, ARROW_RIGHT, DOWN, ARROW_DOWN, INSERT, DELETE, SEMICOLON, EQUALS, NUMPAD0, NUMPAD1, NUMPAD2, NUMPAD3, NUMPAD4, NUMPAD5, NUMPAD6, NUMPAD7, NUMPAD8, NUMPAD9, MULTIPLY, ADD, SEPARATOR, SUBTRACT, DECIMAL, DIVIDE, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, META, COMMAND, ZENKAKU_HANKAKU

Following Appium Android KEYNAME can be used : UNKNOWN, SOFT_LEFT, SOFT_RIGHT, HOME, BACK, CALL, ENDCALL, DIGIT_0, DIGIT_1, DIGIT_2, DIGIT_3, DIGIT_4, DIGIT_5, DIGIT_6, DIGIT_7, DIGIT_8, DIGIT_9, STAR, POUND, DPAD_UP, DPAD_DOWN, DPAD_LEFT, DPAD_RIGHT, DPAD_CENTER, VOLUME_UP, VOLUME_DOWN, POWER, CAMERA, CLEAR, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, COMMA, PERIOD, ALT_LEFT, ALT_RIGHT, SHIFT_LEFT, SHIFT_RIGHT, TAB, SPACE, SYM, EXPLORER, ENVELOPE, ENTER, DEL, GRAVE, MINUS, EQUALS, LEFT_BRACKET, RIGHT_BRACKET, BACKSLASH, SEMICOLON, APOSTROPHE, SLASH, AT, NUM, HEADSETHOOK, FOCUS, PLUS, MENU, NOTIFICATION, SEARCH, MEDIA_PLAY_PAUSE, MEDIA_STOP, MEDIA_NEXT, MEDIA_PREVIOUS, MEDIA_REWIND, MEDIA_FAST_FORWARD, MUTE, PAGE_UP, PAGE_DOWN, PICTSYMBOLS, SWITCH_CHARSET, BUTTON_A, BUTTON_B, BUTTON_C, BUTTON_X, BUTTON_Y, BUTTON_Z, BUTTON_L1, BUTTON_R1, BUTTON_L2, BUTTON_R2, BUTTON_THUMBL, BUTTON_THUMBR, BUTTON_START, BUTTON_SELECT, BUTTON_MODE, ESCAPE, FORWARD_DEL, CTRL_LEFT, CTRL_RIGHT, CAPS_LOCK, SCROLL_LOCK, META_LEFT, META_RIGHT, FUNCTION, SYSRQ, BREAK, MOVE_HOME, MOVE_END, INSERT, FORWARD, MEDIA_PLAY, MEDIA_PAUSE, MEDIA_CLOSE, MEDIA_EJECT, MEDIA_RECORD, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, NUM_LOCK, NUMPAD_0, NUMPAD_1, NUMPAD_2, NUMPAD_3, NUMPAD_4, NUMPAD_5, NUMPAD_6, NUMPAD_7, NUMPAD_8, NUMPAD_9, NUMPAD_DIVIDE, NUMPAD_MULTIPLY, NUMPAD_SUBTRACT, NUMPAD_ADD, NUMPAD_DOT, NUMPAD_COMMA, NUMPAD_ENTER, NUMPAD_EQUALS, NUMPAD_LEFT_PAREN, NUMPAD_RIGHT_PAREN, VOLUME_MUTE, INFO, CHANNEL_UP, CHANNEL_DOWN, KEYCODE_ZOOM_IN, KEYCODE_ZOOM_OUT, TV, WINDOW, GUIDE, DVR, BOOKMARK, CAPTIONS, SETTINGS, TV_POWER, TV_INPUT, STB_POWER, STB_INPUT, AVR_POWER, AVR_INPUT, PROG_RED, PROG_GREEN, PROG_YELLOW, PROG_BLUE, APP_SWITCH, BUTTON_1, BUTTON_2, BUTTON_3, BUTTON_4, BUTTON_5, BUTTON_6, BUTTON_7, BUTTON_8, BUTTON_9, BUTTON_10, BUTTON_11, BUTTON_12, BUTTON_13, BUTTON_14, BUTTON_15, BUTTON_16, LANGUAGE_SWITCH, MANNER_MODE, MODE_3D, CONTACTS, CALENDAR, MUSIC, CALCULATOR, ZENKAKU_HANKAKU, EISU, MUHENKAN, HENKAN, KATAKANA_HIRAGANA, YEN, RO, KANA, ASSIST, BRIGHTNESS_DOWN, BRIGHTNESS_UP, MEDIA_AUDIO_TRACK, SLEEP, WAKEUP, PAIRING, _MEDIA_TOP_MENU, KEY_11, KEY_12, LAST_CHANNEL, TV_DATA_SERVICE, VOICE_ASSIST, TV_RADIO_SERVICE, TV_TELETEXT, TV_NUMBER_ENTRY, TV_TERRESTRIAL_ANALOG, TV_TERRESTRIAL_DIGITAL, TV_SATELLITE, TV_SATELLITE_BS, TV_SATELLITE_CS, TV_SATELLITE_SERVICE, TV_NETWORK, TV_ANTENNA_CABLE, TV_INPUT_HDMI_1, TV_INPUT_HDMI_2, TV_INPUT_HDMI_3, TV_INPUT_HDMI_4, TV_INPUT_COMPOSITE_1, TV_INPUT_COMPOSITE_2, TV_INPUT_COMPONENT_1, TV_INPUT_COMPONENT_2, TV_INPUT_VGA_1, TV_AUDIO_DESCRIPTION, TV_AUDIO_DESCRIPTION_MIX_UP, TV_AUDIO_DESCRIPTION_MIX_DOWN, TV_ZOOM_MODE, TV_CONTENTS_MENU, _TV_MEDIA_CONTEXT_MENU, TV_TIMER_PROGRAMMING, HELP, NAVIGATE_PREVIOUS, NAVIGATE_NEXT, NAVIGATE_IN, NAVIGATE_OUT, STEM_PRIMARY, STEM_1, STEM_2, STEM_3, DPAD_UP_LEFT, DPAD_DOWN_LEFT, DPAD_UP_RIGHT, DPAD_DOWN_RIGHT, MEDIA_SKIP_FORWARD, MEDIA_SKIP_BACKWARD, MEDIA_STEP_FORWARD, MEDIA_STEP_BACKWARD, SOFT_SLEEP, CUT, COPY, PASTE

Following Appium IOS KEYNAME can be used : RETURN, ENTER, SEARCH, BACKSPACE

Following KEYNAME values can be used : ENTER, TAB, ESC, BACKSPACE, DELETE, INSERT, SPACE, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, F13, F14, F15, HOME, END, LEFT, RIGHT, DOWN, UP, PAGE_DOWN, PAGE_UP, PRINTSCREEN, PAUSE, CAPS_LOCK, SCROLL_LOCK, NUM_LOCK, NUM0, NUM1, NUM2, NUM3, NUM4, NUM5, NUM6, NUM7, NUM8, NUM9, SEPARATOR, ADD, MINUS, MULTIPLY, DIVIDE, ALT, CMD, CTRL, META, SHIFT, WIN

Type a data in an Element.

Value1 : Identifier and name of the element where the data is entered in the form of : identifier=html_reference.

Value2 : data to enter in the field.

Clear (Empty) an Element.

Value1 : Identifier and name of the element to be cleared in the form of : identifier=html_reference.

Hide the currently visible keyboard

The action simulates a user pressing down on the screen, sliding to another position, and removing their finger from the screen. Swipe action can be used neither with unique parameter UP, DOWN, LEFT or RIGHT or with combination of parameter CUSTOM and x1;y1;x2;y2, which are coordinates of origin point (x1;y1) and relatives coordinates of destination point (x2;y2)

Value1 : UP, DOWN, LEFT, RIGHT or CUSTOM.

Value2 : x1;y1;x2;y2 (only used if Value1 is CUSTOM)

Scroll to either an element or a text.

Value1 : Identifier of the element or text where the scroll will move the screen to. Has the form of : identifier=html_reference.

Value2 : Maximum number of scroll that will be performed in order to reach the element. This parameter is used only for APK and IPA applications. It default to 8 if empty or invalid.

Value3 : Scroll offset that will be perform after scrolling to the element. This parameter is used only for GUI applications. Format is 2 integer values seperated by a comma. When empty, the global parameters cerberus_selenium_autoscroll_horizontal_offset and cerberus_selenium_autoscroll_vertical_offset are used to offset to the given values.

Install an application on the mobile.

Value1 : Path to the application to install.

Remove an application from the mobile.

Value1 : Application package name to remove.

Wait for a certain amount of time or for an element to be present on a page.

Value1 : Either an integer that represent a duration in ms, either an Element that we will wait to exist in the form of : identifier=html_reference.

Wait that an element is removed from the page.

Value1 : Element that we will wait to be removed from the screen in the form of : identifier=html_reference.

Wait that network traffic idle. Cerberus will wait until requests are no longer performed. That can be used in order to secure that all page components are fully loaded and does not miss some important resource hits. In order to do so, Cerberus will check periodically the number of hits generated from the application since the beginning of the test case. When the number of hits stops to grow during that period, Cerberus stop waiting and continue the test case.

Parameter 'cerberus_networkstatsave_idleperiod_ms' can be used to change the period in millisecond and 'cerberus_networkstatsave_idlemaxloop_nb' can be used in order to limit those checks after a maximum of iteration.

Call a service (REST, FTP, KAFKA,…​) defined on the Service Library and provide the output within the execution.

Value1 : Name of the service to call.

Value2 : Nb of Event until the action finish. It is only used if the Service is a KAFKA service with a SEARCH method. It correspond to the nb of event the action will wait until it resume to the following controls or actions.

Value3 : Time in second until the action finish.It is only used if the Service is a KAFKA service with a SEARCH method. It correspond to maximum time in second the action will wait until it resume to the following controls or actions.

Will allow you to execute SQL update (insert,delete,update).

Value1 : Name of the database where the SQL will be executed. Database needs to be created into the invariant PROPERTYDATABASE and configured on the corresponding environment.

Value2 : SQL to be executed.

Will allow you to execute SQL stored procedure.

Value1 : Name of the database where the SQL will be executed. Database needs to be created into the invariant PROPERTYDATABASE and configured on the corresponding environment.

Value2 : SQL to be executed.

Will clean and remove files based on a given pattern on the robot side. That allow to prepare that a file do not exist before downloading it, preventing that it name is changed when downloaded.

Value1 : Folder and pattern to be deleted

Will upload a file to a folder located on the robot side. That allow to implement use case where a file needs to be uploaded from the robot side to the tested application.

Value1 : Full name of the target file on the robot side.

Value2 : Content of the file to upload. (in plain text or base64 format)

Value3 : Option in order to trigger a specific behavior. EMPTYFOLDER will empty the folder where the file is located in order to secure that its selection is to be performed in the exact same way (more and more files appearing on the folder may make its selection quite complex).

Will get a list of files located on the robot side. That allow to implement use case where you want to test the content of a file downloaded on the robot side from the tested application.

Value1 : Filename pattern to download.

Value2 : number of files to download.

Value3 : Option in order to trigger a specific sorting behavior when selecting the files.

The Action will return a json file that follow the below json format:

Will allow you to calculate a Property defined in the property section of the test case and optionally update the content using the definition of another property. That action should only be used if you need to force a calculation at a precise timing or if you want to recalculate it with the latest value. A property calculation is automatically triggered when using a property without being forced to use that action.

Value1 : Name of the property to calculate. If the property is already calculated, it will be forced to be calculated again.

Value2 : [Optional] Name of a second property whose definition will be used to affect the property in Value1.

Retrieve the network traffic from Cerberus Executor (when activated at robot level) and calculate a json message that can be used for direct controls on all attached controls. If Robot Executor is not activated, Action will end in NE Status and all attached controls ignored. Once all controls of that action are finished, current content are set back to normal value (could be an html or app page or another service).

Value1 : URL to filter. Network requests will be filtered based on that value. Any url that contain the value1 will be included in the network traffic.

Value2 : [Optional] Flag in order to include the response content of every requests. For speed and performance reason, Cerberus by default will not retrieve the content of every requests. If you want to get them in order to perform some controls on them, you can use that flag.

Allow to index the network traffic content into pieces. This action allows, during a testcase, to define some checkpoint that will isolate the traffic statistics done before and after the index. When the action is triggered, Cerberus save the number of requests performed since the beginning of the testcase in order to index them. When at least an index exist on a testcase, the 'Network' tab displayed inside the testcase execution report allow to filter the various dashboard on a selection of indexes. When that action is performed, the 'setNetworkTrafficContent' action and 'getFromNetworkTraffic' default to the content that occured since that last index created. That action is handy in order to perform a full end user scenario (ex : a customer going through a checkout) and perform control on traffic done only on some isolated part of the scenario. Thanks to that action I can validate that a certain hit has been done on a specific part of the testcase (ex : no hits perfomed during the payment page loading.)

Value1 : Name of the index.

Force current content of the test case on the last service call in a JSON format. That JSON will allow controls on the structure of the last call for both Request and Response including information such as http header, http protocol version, or return code. Any control attached to that action will take json path as element syntax for direct controls. If no calls were performed before that action, action will end in NE Status and all attached controls ignored. Once all controls of that action are finished, current content are set back to normal value (could be an html or app page or another service).

Force current content of the test case to the console logs in a JSON format. That JSON will allow controls on the all the logs collected between each call to that action (logs contents are reset after each call to get them). Once all controls of that action are finished, current content are set back to normal value (could be an html or app page or another service).

Force current content of the test case to the data provided in value1 parameter. It can be any format you need (JSON, XML). All controls attached to that action will point to that data. Once all controls of that action are finished, current content are set back to normal value (could be an html or app page or another service).

Lock the device during the execution

Unlock the locked device during the execution. For APK, capabilities unlockType et unlockKey can be used to unlock devices protected by a key.

Rotate the screen 90 degrees.

Just perform no action. No action will be executed and engine will go to the next action or control

DEPRECATED Action that should no longuer used.

DEPRECATED Action that should no longuer used.

Something is incorrect/missing in this section? Feel free to submit modification.

Property variable allow to have multi row content. As a consequence the full syntax will look like this :

%property.NameOfTheVariable.rowNb.SubData%

%system.XXXX-YYYY%

Examples

You will find below some tricks which help you to implement specific test cases.

Something is incorrect/missing in this section? Feel free to submit modification.

This is used to store the test data directly inside Cerberus. This is considered as being static as it will require to define manually each data inside Cerberus. No specific configuration needed, just feed static sub data values in subdata tab.

NOTE : You can define as many INTERNAL data lib entry as you want be giving them the same name. That way, Cerberus will be able to pick one of them from that list (just like it would for the dynamic type such as SQL, SRVICE or CSV).

This is used to retrieve the test data in a dynamic way from any database that has JDCB driver available (it still require Glassfish configuration to create the corresponding connection pool). The SQL will be performed during the test execution to get the data in the right environment at the right timing..

All Subdata now need to be defined in Column with the name of the column where the subdata is defined.

Just like SQL, it will get the data in a dynamic way but from a service call in stead of an SQL. The best option is to define a corresponding service (Service) and point to it (it can then be REST (both GET or POST) or SOAP).

But you can also directly define a Service call request (Service Path, Method and Envelope) if it is in a SOAP format.

All Subdata now need to be defined in Parsing Answer with the xpath or jsonpath where the subdata is defined.

Just like SQL and SERVICE, it will get the data in a dynamic way but from a csv flat file (that can be static or dynamic). Just define the path to the csv file and separator used.

All Subdata now need to be defined in Column Position with an integer that define the number of the column where the subdata is defined.

Database can be configured for data library of types : SQL, SERVICE and CSV. It is used in order to make the access to the data linked to the environment so that, a testcase executed in PROD environment will not call the same URL (or access the same JDBC ressource) as in UAT.

In that example, CRB database has been defined and as a consequence, CSV URL has been modified to be relative.

Databases can be created inside invariant screen. Use PROPERTYDATABASE idname.

Once the database is created in invariant table and used inside the test data library, you can define the context of the data access calls for each environment (System + Country + Environment) inside the Environment screen for the 3 types of datasource :

Something is incorrect/missing in this section? Feel free to submit modification.

This correspond to the URL that points to the page where a new bug can be created on the Bug system of the application.

The following variables can be used inside the URL :

Something is incorrect/missing in this section? Feel free to submit modification.

When producing an event to Kafka, you should define :

When searching an event from Kafka, at the action level you will be allowed to provide :

Cerberus will wait until either the number of event retrieved or time is reached.

When a test case contain a callService action with a KAFKA SEARCH method, at the beginning of the execution, Cerberus will automatically store the latest offset of each partition of the selected topic. When the action is reached, Cerberus will automatically search the events starting at the previously saved offset. That prevent Cerberus to search on the full list of events inside the topic securing performance of the test over time.

Additionally, you can filter the event with 2 method :

Avro Support

Cerberus support Avro data serialization system. You can just activate the feature by checking the corresponding checkbox and feed the Avro Schema registry URL. Cerberus will automatically generate the necessary Kafka Property in order to configure it.

Something is incorrect/missing in this section? Feel free to submit modification.

Calling the associated public service.

Something is incorrect/missing in this section? Feel free to submit modification.

Something is incorrect/missing in this section? Feel free to submit modification.