| # BFlow Test Recorder (tlrgt1290m000) Use this session to record a Bflow test. This session is only supported in a Web UI User Interface. Package The Package the test will be part of. Package will be set to the package the selected VRC belongs to. An existing or a new additional file. If the additional file is a new one, you must also specify a description, otherwise the description of the selected additional file is shown. The specified additional file must have a ‘Bflow’ extension. If you specify a new additional file, an entry in the Additional Files (ttadv2570m000) session is generated. A Bflow Test entry in the BFlow tests (tlrgt0120m000) is also generated. Description Description of the additional file. Mandatory if a new additional file is entered. Start Recording Switches the backend to recording mode. Every next user action is recorded. User actions on the Recording Test session are skipped. The idea is to record a test with the test data that will be used when running the test. Start the session that is the starting point of the test that you want to create. The session is displayed with a red bar at the top displaying ‘Recording’. This tells that actions are being recorded. The additional file, in which the recorded test will be saved, is checked out (if SCM is on) when the recording starts. If a check out is not possible, the recording does not start. A message is displayed why the file could not be checked out. In recording mode some actions are not allowed. These actions are not supported in the Bflow xml, so therefore they cannot be translated to Bflow statements. A message is displayed if such an action is triggered. Actions that are not allowed are, for example, Easy Filtering, Personalizing, and GBF related actions. Sessions of type GBF (tree-like) are not supported in Bflow. The session can be started and closed, but no other actions are supported. Stop Recording Stops the recording. The recorded xml is translated to Bflow statements and the additional file is checked in (if SCM is on). During the translation of the Web UI xml to the Bflow xml, skipped actions are logged. After the translation has been finished a message is displayed if actions have been skipped. The message mentions where the log file has been generated. Normally there are no skipped actions. The actions that cannot be translated are already not allowed during recording. But there may be actions that slip through. Also if during the test a session is used that was already open, for example to look up something, the actions on this session are skipped and logged. More theoretically, actions can also be skipped because the Web UI protocol has been changed, attributes are missing that are required for the translation. Change Curr PVRC Starts a dialog where you can change the current VRC. The Current VRC is displayed in the status bar at the bottom of the session. If a new additional file is specified, the file is created within the current VRC. Only additional files that belong to the current VRC can be specified. |