Posted in Learning on June 26th, 2009
There were some issues with using some FP10 methods on one of the classes in the SDK. It was causing some weird results and since I was using both FP10 and FP9 target application it took me a while to narrow the issue down.
Note: ByteArray.clear() method is new since FP10 so don’t use it unless you are building a FP10 targeted application.
I also zipped up the example code that can be found in the SVN into one zip file and provided it along with the two SDK downloads. You’ll find the links in the featured area of the home page of the structured logs google code project.
There is also an updated to the RIALoggerApp that goes along with this update.
Posted in Learning on June 13th, 2009
Both the StructuredLogTestingSDK.swc and StructuredLogTestingToolingSDK.swc have been updated to version 1.1.
The StructuredLogTestingSDK.swc update includes a pretty big performance CPU update for the StructuredLogTarget class.
The StructuredLogTestingToolingSDK.swc receives some bug fixes around the test script box.
Posted in Learning on May 18th, 2009
Today marks the official release of the Structured Log Testing! The release includes a couple of things:
- http://structuredlogs.com/ - Blog,Information,More…
- Code - 2 SDKs
- StructuredLogTestingSDK.swc - The main client side code sdk.
- StructuredLogTestingToolingSDK.swc - The classes used to build visual tools on top of Structured Log Testing data.
Some quick notes about the SDK. It supports ActionScript 3 only projects as well as Flex based projects. The framework has a custom FlexUnit4 test runner to work with unit testing as well as continuous integration setups. There is a lot of example code inside the google code repository both on the client side as well as the example AIR application for building your own custom log viewer.
RIALoggerApp is the AIR application that I use as my testing playground for supporting Structured Log Testing ideas. The AIR application has been updated to work with the latest Structured Log Testing classes.
Posted in Tools on February 27th, 2009
Just kicked off the first meeting about integrating REDBug with the Structured Log Testing SDK. Looking forward to some good examples and visual components to help show how flexible the Structured Log Testing approach can be.
Posted in Learning on December 26th, 2008
The ideas around Structured Log Testing has come out of real world situations of building complex multi-system applications that where hard to test.Â The methodologies developed work not just for complex systems but for simple cases as well.
The approach has pros and cons like any solution to problems in the software realm.Â One of the big benefits of the Structured Log Testing is its flexbility.Â Flexibility on the development and production.Â On the production side I mean building test scripts and getting robust feedback from end users, making not just the developer but having the potential of dev to end users being part of the testing team.
Along with flexibility is using custom tools that are dynamic and morph with the data you are testing.Â For example if you are debugging standard message flows that have distinct visual cues if there are problems, tools can take the standard log statements and create testing views that make sense for that application.