Testing

XDI2 contains tests for basic testing of low-level functionality.

---

For xdi2-core (see here for the test code):

• Tests for all low-level graph operations on all back-end store implementations (in-memory, BDB, etc.)
• Tests to read and write XDI graphs in all supported formats
• Tests for various other core functionality

---

For xdi2-messaging (see here for the test code, and here for the test resources):

Testing of XDI messaging is done in a cycle consisting of 4 steps:

1. An XDI base graph is loaded from a file. This base graph may be empty or already contain some XDI data.
2. An arbitrary number of XDI $set and $del messages are applied to the base graph.
3. An arbitrary number of XDI $get messages are applied to the base graph. Each one of the message is expected to return at least 1 result statement.
4. An arbitrary number of XDI $get messages are applied to the base graph. Each one of the message is expected to return an empty graph.

The cycle is repeated for all XDI base graphs, and for all back-end store implementations (in-memory, BDB, etc.)

---

For xdi2-client:

• Testing mechanism is TBD

---

For xdi2-transport-http:

• Testing mechanism is TBD

---

Besides the programmatic tests, XDI2 also contains the xdi2-webtools component, which sets up XDI endpoints as well as several web-based tools that can be used to test XDI manually.