Jete / News: Recent posts

Updates concerning the v0.3.1 updates for simplifying the DBSetupAction using the file path variable.

Best practices updates including:
- best practices page (more to come)
- system test samples using best practices

Ant explanation for making Jete sample system tests to run from the download.

0.3.1 updates:
Features:
- DBSetupAction interface changes. Added dataFilePath back, for backward compatability (sorry about that) and ease of configuration.
- keep sample company jarfile in build, allows running tests
- downloaded .zip will actually run! However, need to have junit in Ant classpath, and mysql installed.

Cleanup:
- applied some best practices to the sample system tests, hopefully improving readability

Updates to the Jete home page outlining some of the important updates and samples for the 0.2.3 and 0.3 upgrades.

These include:
- ThrowableValidator samples and explanations
- DBSetupAction wrapper samples and explanations
- Samples of simple data type validations (maps, arrays, etc.)
- some documentation updates and explanation changes

0.3 updates:
Features:
- ***** IMPORTANT ***** DBSetupAction interface changes.
-- May take a DataSet wrapper for simplifying DataSet access. This isn't really necessary, but when using complex datasets it's much easier / nicer from a configuration file perspective to have all the various options localized. Recommend using these wrappers, as instantiating the actual datasets could mess up configuration files.
-- May take a raw DataSet configured to the system testers wishes
-- ***** REMOVED **** dataFilePath property, this now depends on the type of DataSet or DataSetWrapper specified
- FlatXmlDataSetWrapper allows specifying only a filepath instead of an actual File instance
- ReplacementDataSetWrapper facilitates standard ReplacementDataSet functionality, also adding default data replacement for objects in the data files. Current default replacements (case sensitive):
-- [null]
-- [date]
- test sample updates
- singleton dbOperationsMap
- sample system test updates showing this functionality
- Updated javadoc... read more

Features:
- Added ThrowableValidator to validated instances when tests expect exceptions. Specify an exception classname and a message, and the validator will recurse the stack trace until an exception with the specified name and message is found. An AssertionFailedError is thrown if the correct exception isn't found.

- Date offset wrapper class for java.util.Date object. Allows one to set date time relative to now, but in the future or past. E.g. Date.setTime(Date.getTime()+offset)... read more

Jete is a Junit based system test framework that leverages Spring to configure specialized test cases for running system and integration tests.

System tests are defined in Spring application context files, configuring Junit test cases with actions and validators.

The Jete System Test framework homepage has been updated with:
- Homepage navigation menu
- Links to samples
- 0.2.2 functionality updates & samples
- Javadoc ... read more

Updates for features and bugs:
Features:
- Added primitive, array, and Map value validating functionality to the results validator by wrapping primitive objects in a simple object wrapper.
This allows method invocation results to be validated on by setting the PropertyValue name to "" or "value". NOTE: array and map validation require specifying "value[X]" where X is an element number for an array or a key for a Map.... read more

Jete is a system testing framework based on Junit and Spring, and integrating dbUnit, HttpUnit (and more to come).

Jete utilizes Spring to configure specialized Junit test cases to perform test actions, and validate those actions. This turns Spring configuration files into system / integration test files, without having to code junit classes.

Jete brings 4 prime benefits to the table:
1. Integration and system testing has traditionally been difficult to test, and expensive to implement for QA, often requiring massive investment of resources for a homegrown framework. Jete makes this framework generic, and with Spring, the ability to customize as necessary.
2. Unit / Integration / System tests are simple Spring XML configuration files, to be written by developers, QA, or any other person.
3. Promotes test driven development by opening up authorship of test case actions and validators derived from requirements.
4. Helps bring about the Springularity.

The homepage has been updated to include a more detailed walkthrough of the samples included with the Jete release.