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

[Read more…]

These builds for both the Emulation Service and Studio feature both enhancements and bug fixes, along with a new installer for the base product that manages MSI upgrade issues.

Flynet Viewer Base Product and Components (Version: 4.1.20)

New Installer – FVSetup.exe (replaces FlynetViewer.msi)

• FVSetup.exe is an MSI wrapper that ensures that the correct version of Windows Installer is available (and upgrades if not)
• Automatically performs upgrade of existing installation, retaining all registry settings while replacing all installation files
• Fully tested from minimal Windows/XP install
  • Upgrades to Windows Installer 3.1 if 2.x installed
  • Provides guide to install .NET Framework 2 SP1 if .NET 2.0 is not installed
  • Requests installation of IIS if IIS component is not installed
  • Guides activation of ASP.NET if not active for IIS
  • Detects and provides guide to installation of Microsoft Management Console 3.0 if not installed

Flynet Emulation Service (FlyServer.exe)

• SCO-ANSI terminal type support added for VT–still requires registry setting for the actual Telnet terminal type (configuration select-VT) to match active host termtype.  Included support adds 1) host macros, 2) SCO color commands and 3) SCO keyboard lock/unlock

FVTerm – Flynet Web Terminal Emulator

• Added improved initial connection to the startup javascript–this is for new connections where there is a sessionkey passed using outside scripting.  When the startup page is loaded with a URL that includes a sessionkey, the session key is used to start the emulation.  In some cases, due to timing, one call to get started with a sessionkey was not enough.  In this build, retry logic has made the initial connection far more reliable.  This is in support of the Flynet Web terminal emulator sharing sessions with a set of web services as part of a work automation design.

Recorder 2.0

• Added VT220 support so that reliable recordings can be made in a VT environment.  Note that the use of keyboard definition files works.   Custom keyboard setups (CustVTKeys.dat in Definitions folder) can now be supported as are frequently encountered in many older Unix applications
• Improved display of the AID key(s) when viewing a recording.  Location and size are improved, and long key strings are supported, which may be encountered in a VT environment.
• Improved usability of the Recording Viewer–page-up and page-down as well as the mouse scroll-wheel are now supported, with improved management of the elevator scroll element.
• PA1 and PA2 keys were added to the recorder (Ctrl-F1 and Ctrl-F2)
• Terminal Emulation had extended color foreground and background attributes backwards–fixed so that colors in extended environments are correct. 

Flynet API Library (ViewerLib.dll)

• New trySetText method–same parameters as the setText method, but will ignore a null text parameter as well as attempts to write to a protected screen field; returns a true if writes successfully, false if one of the above prevents writing.  If the active screen is an unformatted 3270 screen, will perform a putKeys() method and return true.This new method was introduced to better support screen write methods in web services, where a null parameter is accepted as a “don’t write this” and where a host dynamically changing a field to protected shouldn’t break logic on its own.
• SCO-ANSI host-sent macros now supported with the getHostMacro() method, which will return a host-sent macro command or null if none are pending.  Keep calling until any pending macros are all read.

---

Flynet Viewer Studio (Build: 4.1.2.40001)

New Recording Import Helper

• Activated with right-click on Recording (Import/Import New) – provides small modeless window that displays the next unrecognized screen in a recording and simplifies the import, naming and recognition of the screen.
• Get Next button rapidly finds the next unrecognized screen in the recording and imports it
• Automatically runs the Check Recognition scanner detailed below

Check Recognition for Popups and Overlays

• Separate recording analyzer that verifies the existing recognition through all of the screens in a recording
• Final Validation scanner–scans for recognition anomalies to locate popups and overlay screens so that they can be imported and recognized accordingly

Screen Heatmap Display

• Great for analyzing how a screen is used throughout all the recordings
• Right-click a Screen Definition – Display / Display Heatmap
• Current screen display changes to a “heat map” of host screen writes and user data entry, color coded to show which portions of the screen are changed the most
• Scans all associated recordings to produce the source of the heat map

User Navigation Definitions

• New facility for user-defined navigation between screens without the need to specifically record the navigation
• User Navigation Dialog opened with right-click on Screen Definition (Modeling / User Navigation) or in the Navigation view in the “To” list (Add new User Navigation; Override with User Navigation)
• Displays the “from” screen in left pane with thumbnails of possible “To” screens on the right, color coded to match any known navigations.
• User clicks on a “To” screen to add field changes and the Enter key
• A new field change can be initiated with a button or by clicking on a location in the “From” screen view
• User navigation definitions take precedence over any recorded changes and are used in the generation of the navigation code for web services and other generated applications.

[Read more…]