Go to file
Daniel Zaoui 4203336691 Remove references to POSIX 2018-06-04 13:38:11 +03:00
m4 Enabled exactness to use efl beta API's 2015-05-27 13:12:40 +01:00
src Remove references to POSIX 2018-06-04 13:38:11 +03:00
.arcconfig Add arc config. 2015-02-26 13:10:22 +00:00
.gitignore Add first support for Windows and fix many other config stuff 2018-05-20 21:29:45 +03:00
AUTHORS Exactness: initial commit. 2011-12-06 16:05:14 +00:00
COPYING Exactness: initial commit. 2011-12-06 16:05:14 +00:00
ChangeLog Exactness: initial commit. 2011-12-06 16:05:14 +00:00
INSTALL Exactness: initial commit. 2011-12-06 16:05:14 +00:00
Makefile.am Revert "Add check-exactness target with -j support" 2018-06-04 12:11:31 +03:00
NEWS Exactness: initial commit. 2011-12-06 16:05:14 +00:00
README Updated README. 2013-07-31 13:08:21 +01:00
autogen.sh Exactness: initial commit. 2011-12-06 16:05:14 +00:00
configure.ac Revert "Add check-exactness target with -j support" 2018-06-04 12:11:31 +03:00
exactness.pc.in Add first support for Windows and fix many other config stuff 2018-05-20 21:29:45 +03:00


Exactness is a pixel perfect regression testing tool for Elementary based applications.

Exactness works by playing back a recording of an interaction with the
application, saving images from that playback, and comparing the images to the
set of "known to be correct" images. Returning a non-zero return value when it
detects images mismatches and creates "error.html", a file that includes the
list of tests failed, including the base images, the new images, and a visual
"diff" of the images. Exactness also fails in case the tests themselves exit
with a non-zero return value, e.g segfault.

= Modes of operation =

Exactness has four modes of operation, three of which are essential for normal
operation, and the fourth is helpful in some cases, and in general, just pretty.

== List of Modes ==

# record (-r, --record): record a test macro.
# init (-i, --init): run the test macro and take images of the state.
# play (-p, --play): run the test macro, take images of the state, and compare against the base images (took with init).
# simulation (-s, --simulation): run the test macro, showing the process on screen.

= The List file =

The list file contains a list of tests to actually run.
The file format is:
<test name> <test command>
<test name> has to be one word (no spaces), there are no restrictions on the command. The command is executed using "system", so you can set environment variables and generally do whatever you'd like.
Empty lines and lines starting with # are ignored.

Example line:
  box ./elm_edje_player tests/box.edj

= Using exactness =

For the rest of this section we'll assume the name of the list file is

== Recording ==

The first thing to do when running exactness on a new test is generating the
recording file, this is done but running with "-r". New recordings overwrite
old existing recordings so it's always a good idea to backup recordings you are
happy with.
In order to record for a test list run:
  exactness -r tests.txt
Just interact with the application in any way you'd like (it's better to have
short interactions as tests run in real time, so running the tests will be as
slow as your recording).
Press F2 to mark an image taking opportunity (as many times you'd like), this
will cause "init" and "play" mode to take images for comparison. Please refer
to the "Limitations" section below to read more about image taking
Running this will create the "base dir" (see command line options for more info
about how to change it) and populate it with one recording file per test.

== Init ==

After having a recording file for a test you can go on with capturing the base
images. Those images are assumed to be "correct". You should update them when
this assumption is no longer valid (e.g fixed a bug, updated a test).
  exactness -i tests.txt
This will look for recording files in the "base dir", run them, take images of
the application, and put them in "dest-dir/orig".

== Play ==

This is the most common mode of execution. This should be run on a regular
basis, for example in a CI system.
  exactness -p tests.txt
This will look for recording files in the "base dir", run them, take images of the application, put them in "dest-dir/current", and compare them against the
images in "dest-dir/orig". This will fail (and return a non-zero return value)
if any of the tests return a non-zero return value, or if any of the images
in the "current" dir don't match the ones in "orig" dir.
Detecting a failure is the most important role of exactness, so the return
value is very important. Additionally, an error.html file will be created in
the "current" dir, listing the issues in a human-readable form.

== Simulation ==

This mode is a show off and a debug mode. Very useful with the "-v" (verbose)
option that shows the mouse cursor on the canvas and outputs information to
  exactness -s tests.txt
or for verbose mode:
  exactness -v -s tests.txt
This does nothing other than run the tests to screen. No images are taken,
and no report is generated.

== Command line options ==

* -b, --base-dir: The location of the recording files.
* -d, --dest-dir: The location of the base dir for the images (orig/current will be appended).
* -w, --wrap: Use a custom command to launch the tests with, e.g valgrind.
* -j, --jobs: Number of jobs to run in parallel. Very useful when running in init and play mode.
* -r, --record: record mode.
* -p, --play: play mode.
* -i, --init: init mode.
* -s, --simulation: simulation mode.
* -v, --verbose: Show cursor location and output extra information to console.
* -h, --help: Help, and information about more boring options.

= Limitations =

* Animations are very time-specific, you can't really take snapshots of
applications that have animations.
* Exactness is very susceptible to theme/scale/etc. changes, so make sure to
replicate the full environment.
* Only works with Elementary applications.



exactness is a software package aimed to automate Elementary testing
after updating elm code.
The testing process is composed of running widget test,
cycling through API functions, and screenshot are taken on each stage of test.
(on user request with F2 key).

Next, these screenshots are compared with screenshots of widget test
done before the code update.
When exactness detects difference in screenshot comparison,
it means widget layout was changed.
Unexpected layout changes may reveal that something is broken
in the new implementation.

Testing with exactness composed of the following stages:
First, you need to compose a tests (text) file as follows:
Each line begins with test name
second field is test-command and [optional] params.
Any line starting with '#' is a comment (ignored):

# This is a comment line
TestName1 TestCmd [param1] [param2]

Any name/parameter with space, precede space with double backslash (\\)
pager_slide elementary_test --test-win-only pager\\ slide
In this example test name is "pager"
The application is "elementary_test"
with two parameters: --test-win-only pager\\ slide
("pager slide" compose singe parameter, note the \\)

By default, exactness runs through test file and commits all tests specified.
To run selected tests add test name as param to exactness.
More on this later.

Later, you run exactness with the tests file as parameter.
1. Test Recording.
   Done once and exactness user most likely does not need to do this.
   A set of pre-recorded tests already resides under 'data/recording' folder.

   To record a test just issue the command:
   exactness -r [-b BaseDir] TestsFile

   exactness -r TestFileName

   The record file will be produced in the current-working-directory
   for each line in the test file.
   Name of '.rec' file determined according to test name:
   From example on top we have: pager_slide.rec

   To save your recordings in any other directory,
   pass the directory-name as base-dir:
   exactness -r -b /home/username/my_recordings TestFile

   As test runs you may press F2 at any point to set a screenshot.
   (screenshot produced in 'play' stage, set timing of screenshot here)
   However, don't do this while animation is ongoing
   or you get inconsistent PNG output each time test played.

   NOTE: You may change screenshot key from F2 to any other key
         with TSUITE_SHOT_KEY env var.

   After recording a new test you may use 'simulate' option to play test
   with no effect to output files. Simulate option lets you to examine
   a test-play on-screen without actually producing output PNG file.

   To do this just run:
   exactness -s [-b BaseDir] TestFile

   exactness -s TestFile
   This will play all tests specified in TestFile taking '.rec' files in cwd.
   use the -b option to tell exactness to locate '.rec' files elsewhere.

2. Test Initiation.
   The final stage of testing process is based on PNG image comparison
   of original screenshots with current screenshots produced after code change.

   To start you need to produce original screenshot set before code change.
   To do that just issue the command:
   exactness -i [-b BaseDir] TestFile

   This command will play the tests from TestFile and place PNG files
   under 'orig' folders created in current-working-directory.
   You need to do this just once.

   exactness -i TestFile
   (locate '.rec' files in cwd)

   This will produce PNG files such orig/pager_slide_1.png

   By default exactness looks for '.rec' files in current-working-directory
   Use -b DirName to ask exactness to locate the '.rec' files
   in a specific location.

   exactness -i -b ${prefix}/share/exactness/recordings TestFile
   (locate '.rec' in "${prefix}/share/exactness/recordings")

3. Test playing, producing current state PNG files and comparison files (4).
   After doing Test Initiation (2) and updating elementary code,
   you may run tests for current state of elm:

   exactness -p [-b BaseDir] [-d DestDir] TestFile
   Omitting DestDir param will cause exactness place all PNG files
   under (default) folder named 'current'.
   Note that comparing PNG files (4) is also done upon completion of play.
   This will produce comp_*.png files in your DestDir.

   You may put record-files at specific folder with -b (base dir) argument.
   exactness -p -b ${prefix}/share/exactness/recordings TestFile

   Play '.rec' files at "${prefix}/share/exactness/recordings"
   Write resulting PNG files at cwd/current (default) dir
   along with comp_*.png files.
4. Comparing PNG files.
   This is the final stage of testing in which we compare output
   before code update and after the update.
   Following 'play' action, matching PNG files from 'orig' and 'current'
   folder are compared.

   When all comparisons done you get final report of (N) files did not match.
   In case difference was found, you may look at comp_*.png files in DestDir.

5. fail_if(expr) macro:
   You may use fail_if(expr); macro to verify variable value on-the-fly.
   For example, if your code contains:

   char *p;
   fail_if(p == NULL);

   In case (p == NULL), a "fail_TestName.txt" file is crated
   current working directory with a comment specifying the expr/line failed.

   fail_*.txt files are produced only for when expr fails when running.
   When tests completed, the user gets notification message if any tests failed.
   In such case, please review the fail_*.txt files.

6. Running selected tests.
To run selected tests add test name as param to exactness.
Use this option to run selected tests without modifying your test file.
/opt/e17/bin/exactness -s TestsFile TestName1 [TestName2] [...]
TestName param has to match test name given in tests file (1st field)

7. To view exactness help issue the command:
   exactness --help
   exactness -h