A free Demo version of Fluxica Peregrine is available for evaluation purposes. The Demo version is able to demonstrate the functionality of the commercial versions, but it runs with restrictions. The difference between the versions is shown in the table below.
End User License Agreement
The Demo version is available for download after accepting the EULA. The EULA is a product license, not a sale. The EULA can be found here. The EULA is also available as a downloadable PDF file.
Unlike the Fly, Soar and Stook version of the Peregrine program, the Demo version is a trial version that is limited to 10 days after downloading.
The maximum number of test iterations for a single invocation of the Peregrine program determines the quantified (un)certainty of a test. The certainty increases with the number of test iterations. The Demo version is able to run tests of maximally 1E6 iterations.
The maximum number of test probes NP are the last NP test probes that have been injected into the program under test at any given moment in the test cycle. The probe log reports the last NP test probes on test completion or termination. The Demo version allows for logging one test probe.
Stand-alone Application Program
The Peregrine program is a stand-alone application program, it runs locally and all functionality is built into the program. The program does not include any network connection functionality, it can not connect over any computer network and thus can not `call home' over the internet.
A limited version of the Peregrine Reference Manual, which applies to all Peregrine versions, is included in the Demo download as a PDF file. The manual can also be downloaded separately. The download button for the Reference Manual is activated after accepting the EULA above.
A Bash command line script peregrine_auto.sh that automates the installation procedure is included in the download:
Download the peregrine_demo.tar.gz archive file and extract the script file in any directory: $ tar -xf peregrine_demo.tar.gz ./peregrine_auto.sh
If you are using a GUI desktop environment, the script file can also be extracted by double-clicking the archive file, selecting the support directory and then drag-dropping the peregrine_auto.sh script file to the directory where the archive file is located.
To install or uninstall the Peregrine archive file, run the script and follow the instructions: $ ./peregrine_auto.sh
The symbolic links for the Peregrine executable files, header files and library files are automatically created (install) and removed (uninstall) by the script file.
Test Setup from a Bird's Eye View
The test is set up in four steps:
Include the Peregrine header file.
Add two Peregrine code delimiters around the code segment to be tested.
Replace (selected) variables with matching Peregrine Test Probes in the marked out code segment.
The program source code is compiled as usual to create an executable file and is additionally linked against the Peregrine library (C/C++) or preprocessed to include the Peregrine package (Java).
Invoking the Peregrine program and then running the executable file will automatically test the code segment by continuously injecting it with (pseudo-)random Peregrine Test Probes. These probes are generated on-the-fly at high speed by the Peregrine program.
The test continuous until a failure is detected, a timeout is triggered or a specified number of test iterations is reached. A probe log provides the test results for a post-test analysis.