| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
When running the tests, we want them to pick up the local copies of
Endless-0.typelib and libendless-0.so instead of the installed copies.
The tests now also run properly when there are no installed copies.
[endlessm/eos-sdk#321]
|
|
|
|
|
|
| |
Begin by testing the basic accessors and construction.
[endlessm/eos-sdk#1015]
|
|
|
|
| |
[endlessm/eos-sdk#1015]
|
|
|
|
|
|
|
|
| |
The autotools code for running the tests should go in the included
Makefile.am in the test/ subdirectory, so that all those test files
are run and distributed in the same place.
[endlessm/eos-sdk#290]
|
|
|
|
|
|
|
|
|
| |
These are tests for the basic functionality and a few fail cases of
webhelper, by no means exhaustive. There are a few tests that cannot
execute because I do not currently know of any way to catch exceptions
that occur inside GObject callbacks.
[endlessm/eos-sdk#290]
|
|
|
|
|
|
|
|
| |
This adds a script eos-run-test which is adapted from gjs_run_tests,
but does not try to discover the tests itself. Instead, in keeping with
Automake's test suite facilities, it takes the filename of a test to run.
[endlessm/eos-sdk#290]
|
|
|
|
| |
[endlessm/eos-sdk#133]
|
|
|
|
| |
[endlessm/eos-sdk#79]
|
|
|
|
|
|
| |
Unfortunately, most of the getter setter test fail and are commented
out, because of the remove bug in EosPageManager.
[endlessm/eos-sdk#62]
|
|
|
|
|
|
|
| |
Minimum functionality for EosPageManager. Currently uses a
GtkNotebook internally until we decide what to do regarding GtkStack.
(Philip; map/unmap Matt, Patrick)
|
|\
| |
| | |
Fix make distcheck
|
| |
| |
| |
| |
| |
| | |
Header file missing from a _SOURCES declaration, and wrong file name
in POTFILES.in.
[endlessm/eos-sdk#55]
|
|/
|
|
| |
[endlessm/eos-sdk#7]
|
|
|
|
|
|
|
|
|
| |
Add an EosApplication class. Functionality:
- present main application window when activated
- warn if more than one application window is added
Also add a stub EosWindow class that overrides GtkWindow's
"application" property to be a construct-only property.
[#4]
|
|
There are automated tests which run when you do 'make check', and also
smoke tests which demonstrate one piece of functionality, which can be
used as a sort of sanity check or demo.
[#1]
|