1: [[!template id=project
3: title="Create an SQL backend and statisticics/query page for ATF test results"
10: [Martin Husemann](mailto:martin@NetBSD.org)
15: duration="3 months"
18: We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.
19: The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.
20: This is good enough to display single test run results, but does not provide any overview or comparison options across different test runs or architectures.
22: The target of this project is to provide a simple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
23: Creating a suitable database schema and the xml loader/upload tool is the first half.
25: Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
26: to the query pages of typical bug tracking systems.
28: This project has the following milestones, in this order:
30: 1. Create and test a database schema (suitable for multiple architectures, and later migration to Kuya)
31: 2. Create a tool to read the ATF xml data and insert it into a database. This will be the half term milestone.
32: 3. Create a web site providing basic browsing/search options for the database
33: 4. Enhance the upload tool (or create a second variant) for Kuya output. This part is optional
34: 5. Document the database schema, web site setup, and tool created.
36: A huge set of ATF xml data will be provided, we assume that the student creates the database environment for local testing themselves.
38: The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
39: This deployment is not part of the GSoC timeline.
41: Note that item (4) above needs proper evaluation before the database schema is created. Kuya already stores test results in a SQLite database, so the extract and upload utility likely will be simple, but the database schema is incompatible and a good migration plan is needed upfront.
43: During GSoC, this project will ignore deployment issues, which will need broader discussion and maybe changes to the tools - for example the finally deployed upload utility has to be part of the base installation, so may not be able to depend on PostgresSQL libraries. A pkgsrc based solution for milestone (2) is good enough for this project.
47: [[!tag gsoc]]
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb