These builds for both the Emulation Service and Studio feature both enhancements and bug fixes, along with a new Simulated Host Script generator that provides the ability to implement disconnected testing (no host connection needed for initial unit testing). The 4.2G installers were used for a few customer situations; the 4.2H installers include these and are documented in this post.
Flynet Viewer Base Product and Components (Version: 4.1.23)
Flynet Emulation Service (FlyServer.exe)
- Bug fix: 3270 unformatted screens, returned cursor position invalid for lines greater than 1 (no known issues with hosts)
- Help updates to the Developer’s Learning Guide and the Studio graphic for the Flynet Development Lifecycle
- Fix–pooled sessions were not being managed correctly when the host dropped the connection in a certain manner. This would lead to a pool reporting no available sessions, even when sessions were available. Same problem can affect the overal system counter, showing more sessions active in the counter than actually are.
- Added additional logging to session stop and start code to continue to improve session management under odd host connect/disconnect conditions.
FVTerm – Flynet Web Terminal Emulator
- When a requesting page passes an application name and sessionkey in the initial startup, the web services module has been improved to avoid a “non-start” condition, where the browser simply stays on the initial Flynet logo instead of launching into terminal emulation. This non-start condition could occur sporadically depending on timing the host screen transitions.
Recorder 2.0
- The default recorder for the “Blue FV Icon” in the system tray icons is now Recorder 2.0
- Added a Keyboard mapping display and customization dialog–accessed from the Settings menu
- Added information entry similar to Recorder 1.0, including Screen name, short description and comment. Available for each screen–still does not provide recognition but recognition is best managed in Studio as all screens are available for proper analysis of recognition screens (as opposed to one-at-a-time during a recording)
- Information entry is optional and is defaulted OFF – change from the Settings menu to activate
Simulated Host (SimHost) – New Script Version 2.0
- Added new script elements and attributes to support the new FV Studio Simulated Host generation support. The approach of the new tags is to ensure that each defined screen in the user project has one entry in the Simulated host script. A context is maintained from all original recordings, allowing superior reproduction of the host responses to user input.
- While the new SimHost is now more accurate, it is also more “picky” about all screen entries being exactly as they were when initially recorded. For this reason, the Test Case generator tool has been provided and integrated with the FV Studio GUI task testers.
Flynet Viewer Studio (Build: 4.1.2.40100)
New Simulated Host Script Generator
- Replaces the original Simulated Host Script Generator launched with the Export / Simulator Script menu option in FV Studio. Since many issues with the original generator have been solved through design changes, no longer runs as a wizard, but a simple file-save dialog. Generates scripts with far better accuracy and completeness while still allowing upgrades through user editing.
- A script can be updated with additional recordings without affecting user edits–this is performed using the same pulldown menu, and a prompt is provided for an existing script file; to update it or create fresh.
New Test Case Generator
- Will read through all the provided recordings, and using start points and the active “home page” definition, will create a batch of XML files containing parameter values
- Each Task project has a new menu option to generate Test Cases for that project
- When Testing an individual Task, the GUI Task tester first page will “find” the qualifying test cases by filtering them based on the screens represented in the test case (the data entry screens need to match the data entry screens for the task)
Recording Import Helper
- Will add a recording to the active application project if selected from the Recordings tab (and the recording isn’t currently in the list of active recordings)
Screen Heatmap Display
- Added right-click to save as JPG for easy access concurrent with other FV Studio activities, such as Screen Field mapping
User Screen Change Dialog
- Added a Close button to make it easier for users looking for a specific button instead of using the X icon upper right of the window. The User Screen Change dialog usability is still in need of improvement, as the status of change definitions is not clear to the user.
Web Service Generator Projects
- Fixed some navigation regressions, improving the accuracy and speed of navigation in the generated project
- Fixed data entry for VT (character entry) write screens when a single field is being written
- Enabled selection of the Pool name and Host name by surfacing properties in the TaskSession class of the generated solution
GUI Task Tester
- The first page of the Task Tester (Parameters) now has additional buttons to A) browse and copy parameters from the generated test case folder and B) Save the current parameter set as a named test case. This provides rapid, repeatable and convenient testing capabilities across a broad spectrum of data entry combinations.
Miscellaneous Fixes
- The new user-defined navigation entries were not being saved and restored properly when the application was saved and then reloaded
- The View-in-Linker thumbnails, when magnified, were doing a transition to the next screen in the linker (recording)–this made it difficult to properly view the screen. The transition effect was introduced in the Task definition “OKScreens” wizard, and for it to run at other times was a regression (fixed now).
- When entering the name of a new Solution, if the user backspaced to where there was no text in the Name field, an exception was being thrown
- Each time a Web Service was generated, the “dirty” flag on the active application was being set, even if no changes were made to the application. This would result in a “Save XYZ?” message on closing, which only should be displayed if a real change has occured. This has been fixed so that the “Save?” message is only displaye when there unsaved changes actually exist.