Change Log and History ====================== Version 0.1.4 / 2012-08-06 -------------------------- This release introduces the ability to be a little more flexible and expansive with the locators that are used as well as to allow custom locators by mapping them to existing locators. Partial support has also been added for using CSS selectors, although it is questionable if that will ultimately remain. This is a start at cleaning up the logic regarding how locators are currently handled for the various web objects. Version 0.1.3 / 2012-07-15 -------------------------- This release introduces a lot of low-hanging fruit. For example there is now the ability to get the title, markup and the active URL of a page. There is also the ability to get a screenshot. It is also possible to get the tag name from a web object. As far as web objects, the ability to get and set values for text fields is now in place. I've also added the ability to execute specific JavaScript calls against the browser. This helps determine what web object currently has focus, as just one example. A DataSetter module has been added to allow for easier population of data elements. The idea here is that a using method -- called against a page or activity definition -- can send data directly to web objects on that definition. This is just the start of a streamlined approach for populating data a bit easier than was previously the case. I have also made sure to update to the latest watir-webdriver. Version 0.1.2 / 2012-06-06 -------------------------- This release provides a new Locators module. The idea behind locators is that undeclared web objects can be used by providing a direct locator reference. Also new in this release is the ability to handle JavaScript alert, confirmation, and prompt message boxes. Finally, table logic was enhanced to allow tables to be enumerated as well as to allow text cells to be referenced by named columns and rows. Version 0.1.1 / 2012-05-30 -------------------------- This release provides a series of "wait state" methods in order to check for certain conditions, such as an object being visible. The library is now able to get the attribute and style information from web objects. A start has been made on the idea of browser-level actions and page-level actions. These are lumped together under a module called Evaluators. The sample test application being used for Symbiont acceptance tests is now included as part of the application. Version 0.1.0 / 2012-05-16 -------------------------- This release marks the start of alpha testing for the Symbiont library. Symbiont is now able to work with many primary web objects. This release also contains a full set of acceptance tests for current Symbiont functionality (see specs directory) as well as a full set of unit tests (see spec directory). Symbiont versions will only be released if there is one hundred percent unit coverage and an acceptance test for each added or modified feature. Version 0.0.4 / 2012-04-14 -------------------------- A very minor update to make sure all tests are in place and working correctly. This release is in preparation to getting the minor release schedule going. Version 0.0.3 / 2012-04-11 -------------------------- Symbiont went in a different direction, which is excluding Selenium and focusing on Watir. Watir is simply a cleaner API that makes for a more consistent implementation. The focus here was on getting the basis for the generators and enclosers in place. The idea of page and activity definitions that serve as action contexts was also put in place. Version 0.0.2 / 2012-03-15 -------------------------- This implementation of Symbiont is designed to show the basics of how platform objects, web objects, and a generator mechanism work together to create a test script style that normalizes execution with Selenium and Watir and provides a convention-based approach to interaction with browser objects. Version 0.0.1 / 2012-03-02 -------------------------- This is a bare implementation of the Symbiont library. The Symbiont library is one part of what will be the Lucid testing framework. This release does nothing beyond establishing the gem and providing some basis for how the library will work.