Stadium3 Release : 3.3.1983.4381

Build 3.3.1983.4381 is available for download. It includes:

• Designer - Fix for error that occurred when 'Events' window was closed 
• Date format for all date fields can now be set to 'dd/MM/yyyy'

All date fields till now have always been displayed in 'yyyy/MM/dd' format. This can now be changed to 'dd/MM/yyyy' by adding below setting in web.config:

  <appSettings>     .......................

    <add key="DateFormat" value="dd/MM/yyyy"/>
  </appSettings>

Please note that Sql server queries work with format 'yyyy/MM/dd'. If you are using the new format, all sql queries will have to be modified to use 'convert' function. Stadium format conditions with date values will also have to be changed to conform to dd/MM/yyyy format.

Stadium4 Release : 4.1.2119.4736

Build 4.1.2119.4736 is available for download. It includes:

• Designer - Fix for error that occurred when 'Events' window was closed
• Chart control - Small changes to visual display
• Grid control - Height and width in percentages now work
• Menu item editor - Auto populates 'Text' property when 'DestinationPage' is selected
• Date Format - Date format for all date fields can now be set to 'dd/MM/yyyy'

All date fields till now have always been displayed in 'yyyy/MM/dd' format. This can now be changed to 'dd/MM/yyyy' by adding below setting in web.config:

    <appSettings>     .......................
        <add key="DateFormat" value="dd/MM/yyyy"/>
    </appSettings>

This setting will be in web.config file for a clean install but needs to be added for an upgrade.

Please note that Sql server queries work with format 'yyyy/MM/dd'. If you are using the new format, all sql queries will have to be modified to use 'convert' function. Stadium format conditions with date values will also have to be changed to conform to dd/MM/yyyy.

Stadium4 Release : 4.1.2110.4717

Build 4.1.2110.4717 is available for download. It includes:

• Command editor - Ordering of stored procs is per schema now
• Application name is now populated automatically when uploading a sap file
• DataGrid dropdown columns can have different values based on data in another column
• Fix for detailsview readonly field becoming editable when page is refreshed
• Maintenance message is now not displayed when assigning access rights to a role in an application
• Treeview node click event is fired when loading page if SelectedNodePath has been set by default
• Button - BackColour property works now
• Panels with percentages for width and height works correctly now
• Grid borders now display correctly in IE 8.0
• Cross-site scripting security fixes
• Chart - Border property has been removed
• Chart - Default colour palette has been changed

Stadium3 Release : 3.3.1977.4368

Build 3.3.1977.4368 is available for download. It includes:

• Fix for detailsview readonly field becoming editable when page is refreshed
• Maintenance message is now not displayed when assigning access rights to a role in an application
• Treeview node click event is fired when loading page if SelectedNodePath has been set by default
• DataGrid dropdown columns can have different values based on data in another column

Stadium as a Test Management Tool

Test Management is a crucial task and is necessary for every software development organisation’s QA process. It involves many tasks including writing Test Cases, documenting Test Run Results, logging Issues and producing Test Summary Reports.

It is necessary to find software that can manage these simple, yet crucial, tasks. I did some research on the test management tools that are available on the market. Most tools require you to purchase a license which does not come at a cheap price for commercial users. So, I thought, what can be better than using our in-house product, Stadium, as a Test Management tool?

The versatility of Stadium has brought a whole new level in this scenario.

I started by listing out the tasks that a typical Test Management tool should do. Among the main tasks are:

• Creating and Maintaining Test Cases
• Documenting Test Results
• Logging Issues
• Generating Reports

Next, I created database tables that would store all the information. For example, a TestCase table would consist of the following fields:

• Test ID
• Description
• Pre-Requisites
• Steps
• Expected Results
• Stadium Version

The last step is to set up the pages in Designer. Look at the screenshots to see Digiata’s very own Test Management tool!

1.       Test Case Management

Users can view Test Cases that are added previously and filter according to keywords they prefer.

They can also add their own set of Test Cases.

The tool also allows users to update existing Test Cases.

2.       Test Run Management

Users can view latest Test Runs according to the date that the tests were executed and status of the Test Cases.

While running the tests, they can log the status in the following page.

3.       Issue Tracking

The tool allows users to view status of the Issues that were logged previously.

Users can log new Issues for Failed Test Cases.

Users can update the Issue status. For example, if an Issue is being fixed by the developer, the status can be changed to Dev. Other status for Issues includes - Ready (If the fix is ready to be tested) and Closed (If the Issue has been fixed).

4.       Viewing Reports

Users can view Test Result summary on the Reports Page. It consists of a pie chart displaying the status and a list of Test Cases according to their status.