AFTER is a configurable test engine written in Ruby. Libraries can be added to facilitate testing against any application type. It also allows for test scripts to be written in any format provided there is an associated script reader for that format.
Be the first to post a text review of Automated Functional Test Engine in Ruby. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Today marks a big achievement for AFTER. Today we passed 100 downloads. With that though I would put a call out to those that have downloaded. Can you please give us some feedback of whether you loved it or hated it. We are really trying to chart the direction for the future and would really appreciate the input of the community that is using it. We are presenting AFTER at the Google Test Automation Conference in August and would like to incorporate some community feedback before then. Thank You!!
This is a pretty minor release. Only two things of note were included in this release. First support was added for loops in scripts. Second component libraries were created for use with FireWatir. This now allows AFTER to interact with Firefox.
0.1.2007.0426 ------------- *Removed include statements for REXML and Log4r and instead reference them directly using :: syntax. This was to fix problem with conflicting class names between REXML and FireWatir. *Created FireWatir component libraries to support Firefox. *Created FireWatir examples to demonstrate Firefox support. *Added support for For loops within the test scripts. Added example in EXE example script. 0.1.2007.0329 ------------- *Refactored TestEngineCore.rb into several new objects to make engine more object oriented. *Created TestEngine class as singleton that handles all things pertaining to the engine itself. (i.e load config file, initialize logger, store reference for results manager, determine script reader type) *Created Script Runner class that is responsible for loading the scripts and then reading every test step. *Created TestStepRunner class that handles running the current test step and retaining the results for the ScriptRunner to handle. *Created TestStep class which holds the information for the current test step. *Created config file for use with the engine and for defining information needed by log4r. *More extensively integrated log4r in engine. *Created EngineLogger class that is used to handle multiple loggers and custom levels. It serves as a proxy class between the engine and log4r. *Created base ScriptReader class so that the scripts can be written in other formats and can be read by creating a ScriptReader. *Created XmlScriptReader to handle current test scripts. *Changed tests and test node in scripts to be teststeps and teststep respectively. *Changed component library starter files to be a class rather than a module. Also added GetObjectReference to class so that I can return the reference and store it in the test engine class. 0.1.2007.0320 ------------- *Developed core engine files. *Added WATIR component libraries *Added EXE component libraries *Added WATIR examples *Added EXE examples *Integrated log4r logging *Added support for relative paths within scripts and TestEngineStarter.rb *Added unit tests to test directories *Restructured directory output *Created installer
0.1.2007.0426 ------------- *Removed include statements for REXML and Log4r and instead reference them directly using :: syntax. This was to fix problem with conflicting class names between REXML and FireWatir. *Created FireWatir component libraries to support Firefox. *Created FireWatir examples to demonstrate Firefox support. *Added support for For loops within the test scripts. Added example in EXE example script. 0.1.2007.0329 ------------- *Refactored TestEngineCore.rb into several new objects to make engine more object oriented. *Created TestEngine class as singleton that handles all things pertaining to the engine itself. (i.e load config file, initialize logger, store reference for results manager, determine script reader type) *Created Script Runner class that is responsible for loading the scripts and then reading every test step. *Created TestStepRunner class that handles running the current test step and retaining the results for the ScriptRunner to handle. *Created TestStep class which holds the information for the current test step. *Created config file for use with the engine and for defining information needed by log4r. *More extensively integrated log4r in engine. *Created EngineLogger class that is used to handle multiple loggers and custom levels. It serves as a proxy class between the engine and log4r. *Created base ScriptReader class so that the scripts can be written in other formats and can be read by creating a ScriptReader. *Created XmlScriptReader to handle current test scripts. *Changed tests and test node in scripts to be teststeps and teststep respectively. *Changed component library starter files to be a class rather than a module. Also added GetObjectReference to class so that I can return the reference and store it in the test engine class. 0.1.2007.0320 ------------- *Developed core engine files. *Added WATIR component libraries *Added EXE component libraries *Added WATIR examples *Added EXE examples *Integrated log4r logging *Added support for relative paths within scripts and TestEngineStarter.rb *Added unit tests to test directories *Restructured directory output *Created installer
Just a quick announcement to mention that today we are happy to welcome Michael Ilfrich to the development team. Michael will be trying to put together a UI for the scripts to make it a little easier to build them.
Several new subprojects have been added to AFTER to track other projects that are tied in with AFTER. These include a UI so that test can be created, documentation, and adding to the two component libraries that currently come with AFTER. Take a look under Tasks to see all the subprojects and if you are able to help out with any of them let us know. We can always use some good help.
0.1.2007.0329 ------------- *Refactored TestEngineCore.rb into several new objects to make engine more object oriented. *Created TestEngine class as singleton that handles all things pertaining to the engine itself. (i.e load config file, initialize logger, store reference for results manager, determine script reader type) *Created Script Runner class that is responsible for loading the scripts and then reading every test step. *Created TestStepRunner class that handles running the current test step and retaining the results for the ScriptRunner to handle. *Created TestStep class which holds the information for the current test step. *Created config file for use with the engine and for defining information needed by log4r. *More extensively integrated log4r in engine. *Created EngineLogger class that is used to handle multiple loggers and custom levels. It serves as a proxy class between the engine and log4r. *Created base ScriptReader class so that the scripts can be written in other formats and can be read by creating a ScriptReader. *Created XmlScriptReader to handle current test scripts. *Changed tests and test node in scripts to be teststeps and teststep respectively. *Changed component library starter files to be a class rather than a module. Also added GetObjectReference to class so that I can return the reference and store it in the test engine class. 0.1.2007.0320 ------------- *Developed core engine files. *Added WATIR component libraries *Added EXE component libraries *Added WATIR examples *Added EXE examples *Integrated log4r logging *Added support for relative paths within scripts and TestEngineStarter.rb *Added unit tests to test directories *Restructured directory output *Created installer
Starting with this release we will not only have available a windows installer but we will also make available a zip file so that our non windows friends can run the engine as long as their system can run Ruby.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?