Less4j-release-tests project contains long running tests for less4j. There is no reason to run them together with unit tests, but they should be run before each Less4j release.
Less4j-release-tests works only if:
- latest less4j code is stored in the same directory,
- git is installed and accessible from command line,
- maven is installed and accessible from command line,
- java is installed and accessible from command line.
Note: less4j-release-tests works inside ..\less4j-release-tests-working-dir directory. Do not store anything is it, the project can recreate and delete its content any time it runs.
Directory structure after tests have been run:
-- workspace
|-- less4j
|-- less4j-release-tests
|-- less4j-release-tests-working-dir
The project has two test cases:
- check less4j Twitter Bootstrap compatibility,
- check optional dependency.
LessFrameworksTest test case compiles Twitter Bootstrap v2.3.1 with both less-1.3.3.js and latest less4j. The test then checks generated css files for compatibility.
Checks compilation compatibility of two Bootstrap files:
- test 1: bootstrap/less/bootstrap.less,
- test 2: bootstrap/less/responsive.less.
Steps in details:
- clone or update Twitter Bootstrap repository,
- checkout tag,
- compile with less.js,
- compile with less4j,
- normalize and compare results.
Less4j has one optional dependency - JCommander which parses command line arguments. Normal non-command line version is not supposed to use its classes. OptionalDependencyTest test case creates an instance of programmatic less4j and uses it to compile small less file. If the compilation hits any class from the optional dependency, 'class not found' exception is thrown.
Steps in details:
- compile less4j,
- download all non-optional dependencies,
- load less4j jar and all jars with dependencies,
- create compiler instance,
- compile small less.
Issues are tracked in Less4j issues tracker.
Public domain.