| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
In order to prevent collisions between configuration directories, the
test applications get unique IDs from not just g_get_real_time(), but
also getpid()
|
| |
|
|
|
|
|
| |
Running tests with the same application ID causes DBus collisions.
Apparently this did not cause problems until now.
[endlessm/eos-sdk#303]
|
| |
|
|
|
|
| |
Begin by testing the basic accessors and construction.
[endlessm/eos-sdk#1015]
|
| |
|
|
| |
[endlessm/eos-sdk#133]
|
| |
|
|
| |
[endlessm/eos-sdk#79]
|
| |
|
|
| |
[endlessm/eos-sdk#88]
|
| |
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
| |
Test harness improvement: ADD_APP_WINDOW_TEST(test_path, test_func)
creates an EosApplication and connects test_func() to the "startup"
handler of the application, then runs it.
Commented out /application/two-windows test, because it's apparently
not deterministic.
|
| |
|
|
|
|
|
|
|
| |
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]
|
