Awlsim development
Back to the Awlsim home

Latest bleeding edge awlsim can be downloaded using the Git version control system as follows:

via https:
git clone https://git.bues.ch/git/awlsim.git
or via http:
git clone http://git.bues.ch/git/awlsim.git
or via git:
git clone git://git.bues.ch/awlsim.git

or by downloading the awlsim snapshot archive.
To browse the Git repository online, go to the git web interface.
A mirror of the repository is available on GitHub, GitLab, Bitbucket and on NotABug.org.
If you want to contribute to awlsim, please read the contribution guidelines first.

If you find any bugs in awlsim or if you have any suggestion for new features, we would like to hear from you.
Your help is greatly appreciated and will help to create better software and improve the overall experience for everybody. So don't hesitate to report anything that that limits your awlsim usage.

If you have got any code improvements or other improvements that should be merged into the project, please send such enhancements to the awlsim maintainer.

Please read the contribution guidelines first.

Awlsim is a complex piece of software. The following two diagrams show the basic connections and interactions between the basic parts of the software package. (Click to enlarge).

Awlsim has unit tests for all of its core features. The test suite is located in the tests subdirectory of the source tree.
The test suite currently comprises about 150,000 lines of test code.

The testsuite can be run using the tests/run.sh script. Optionally the -q option can be supplied to run.sh so that a quick test is done.

For core features it is an absolute requirement to have complete tests before a new feature can be merged.

For the GUI (graphical user interface) there currently are no automated tests. That is unfortunate and will have to change in the future, so that GUI features can automatically be validated, too.

Updated: Tuesday 15 August 2017 20:20 (UTC)
https (TLS/SSL)
xhtml / css