| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
There are errors with multiple docbook xml file while
make documentation.
../node-startup-controller-docs.xml:10: parser error :
XML declaration allowed only at the start of the document
Signed-off-by: Phong Tran <tranmanphong@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous docs format, CC 1.0, is not recommended by GENIVI, and
the preferred one is CC-BY-SA 4.0.
Other license changes are:
* Add Creative Commons copyright headers to documentation.
* Add copyright headers to test code.
* Add copyright headers to dbus XML that belongs to the NSC.
* Update copyright headers to GENIVI's standard.
Notable exceptions are:
* dbus XML that is used to communicate with other services
(e.g. common/nsm-consumer-dbus.xml) has not had copyright statements
added, because the Node Startup Controller does not own that interface.
|
| |
|
|
|
|
|
| |
Make sure we use the same spelling of focussed in all places to
avoid confusion.
Signed-off-by: Erik Botö <erik.boto@pelagicore.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This commit simplifies the build process by adding an autogen script
to handle the creation of an m4 directory and execution of gtkdocize
and autoreconf.
Documentation on building has been updated accordingly.
Signed-off-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
Signed-off-by: Jannis Pohlmann <jannis.pohlmann@codethink.co.uk>
|
| |
|
|
|
|
|
| |
In test-legacy-app-handling.xml, the timeout was wrong.
In test-target-startup-monitoring, the phrase "Applied the node state N"
had been changed to "Node state N applied" in everywhere but one place.
|
| | |
|
| |
|
|
|
| |
Replace the old DLT messages in the TargetStartupMonitor test case
documetnation with the ones we currently use.
|
| |
|
|
|
| |
Add a dedicated COPYING.docs file for this. The license is also
mentioned again in the reference manual itself.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed the requirement to restart the system for each test, instead
just restart the node startup controller for each test. The downside of
this is that the dlt.log file is not reset so may become very large.
Reduced the number of DLT log messages to compare against the output.
Instead, only the most relevant lines are included for each test.
Added separate test that the Node Startup Controller registers itself.
Rewrote the descriptions for each test case to be more readable.
Numbered each test case.
Spelling and grammar fixes.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Fix in Test legacy app handling documentation the purpose, some
error logs and some commands.
Fix duplicate will in about.xml
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Changes the single instance of "we" in this file.
Minor grammatical fixes.
|
| |
|
|
|
|
| |
It now uses passive language throughout.
Other minor grammatical fixes
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Replace the previous title by "Tests for legazy application handling".
Fix some paragraphs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Test titles are made more descriptive by including the name of the node
state which is being set.
A link is included to the enum which defines the NSMNodeState.
Tests are changed to always set the node state. This is done by
starting the unit twice in most cases. In addition, the less-important
lines in the DLT log output are no longer specified.
Capitalization in titles has been cleaned up somewhat.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the documentation for legacy app handling tests.
The following tests are provided:
1. Register a normal and a fast shutdown consumer.
- Check that node-startup-controller.service registers itself
as a shutdown consumer.
- Check that the registration for the shutdown consumer are ok.
- Check that in the process of shutting down the fast consumers
shutting down first and the normal consumers second.
- Check that the shutdown consumers are unregister as a shutdown
consumers when they have been shutting down.
- Check that node-startup-controller.service unregisters itself
as a shutdown consumer when it has been shutting down.
2. Register two normal shutdown consumers
- Check that in the process of shutting down the consumers are
shutting down in reverse order of registration.
3. Register a shutdown consumer twice within different modes and timeouts
- Check that the re-registration modify the final mode to a combination
of both modes (normal and fast) and the timeout has been set to the
last registration value of timeout.
- Check that in the process of shutting down the consumer is shutting down
for the both modes.
4. Register a shutdown consumer with invalid arguments
- Check that register a consumer without unit name fails.
- Check that register a consumer within mode 0 fails
- Check that register a consumer with a negative timeout fails.
|
| |
|
|
|
|
| |
Modify in the documentation for legacy app handler that timeout is a
non-mandatory legacy app handler argument and its default value is
1000 milliseconds.
|
| | |
|
| |
|
|
| |
Tests are restructured in the same way as the previous commit
|
| |
|
|
|
|
|
| |
Test cases are restructured into:
* Description
* Test Commands
* Desired behaviour and Output
|
| | |
|
| |
|
|
| |
Also fix a mistyped systemd command.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each test scenario (i.e. luc, legacy app, tsm) has been split into a
separate file.
Setup steps which have to be performed for every scenario are moved into
test-general-setup.xml
Cross-references are used so that the test overview links to each test
case, and the "Testing" page links to the general setup and also each
test.
test-example has been removed because it is no longer necessary.
|
| |
|
|
|
|
|
|
|
|
| |
The following test scenarios are added to the documentation:
* Registration of a simple dictionary
* Registration does not happen on an isolated RegisterWithLUC() call
* An isolated FinishLUCRegistration() call will not change the LUC
* Registration of a complex dictionary
* Registration can happen with a series of RegisterWithLUC() calls
* Repeated registration of an app changes the order in the LUC
|
| |
|
|
|
|
|
|
|
|
|
| |
Explicitly states the difference between the Node State Manager Dummy
and the real Node State Manager, i.e.
* The NSM dummy toggles between successfully setting the node state
and failing to set the node state.
* The NSM dummy toggles between the LUC being required, and the LUC
not being required.
* The NSM dummy will shut down its fast shutdown clients, then its
normal shutdown clients, on receiving the SIGHUP signal
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The improvements to the layout of the test document are that the
individual tests will now show up on the table of contents.
The Target Startup Monitor (TSM) tests check that the following cases
attempt to change the node state:
* The Node Startup Controller starting
* focussed.target starting
* unfocussed.target starting
* lazy.target starting
The following case should not attempt to change the node state:
* focussed.target stopping
|
| |
|
|
| |
Lays out the structure of the test document XML
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This includes mostly files, directories and the package/tarball name.
The classes and D-Bus interfaces will be renamed in the next step.
|
| |
|
|
|
|
|
|
|
|
| |
It seems like the "active-state" property might be part of the
invalidated properties, not the changed ones. By passing
G_DBUS_PROXY_FLAGS_GET_INVALIDATED_PROPERTIES to the proxy constructor
we force GDBusProxy to retrieve the new "active-state" value before
calling "g-properties-changed".
Hopefully this will fix TargetStartupMonitor for real.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Most of the chapters in this manual still need to be written but this
is a start.
|
|
|
This includes adjusting the configure script to check for gtk-doc as
well as creating the necessary directories and Makefile.am files.
At the moment, no documentation is generated. We'll have to add initial
templates that include the docbook XML generated for the D-Bus API.
|
