Differences

This shows you the differences between two versions of the page.

--- civilinfrastructureplatform:ciptestingmanagement [2017/05/30 22:49]
Agustin Benito Bethencourt
+++ civilinfrastructureplatform:ciptestingmanagement [2017/08/24 15:00]
Agustin Benito Bethencourt new links to management pages
@@ Line 1: / Line 1: @@
 ====== CIP testing management ======
+===== Board At Desk planning and progress =====
+In this section you can follow how the project is progressing and the plans for the coming weeks. As described in the [[ciptesting|CIP Testing project description page]], 4 actions describe what this effort is about. These actions have been decomposed into several milestones, described below. Please take **dates as estimations and early plans, not commitments**. Check the diagram for further detail:
+{{ :civilinfrastructureplatform:cip_testing_project_planv0_2.jpg?1000|CIP testing high level action plan  }}
+   * B@D Improvements (orange): tasks related with updating B@D and adding new functionality requested by CIP Members or required to accomplish the overall goals (again, described in the [[ciptesting|CIP Testing project description page]].
+   * Action 2 preps and signing (gold/pear): preliminary tasks to configure B@D capabilities needed to reach the goals of this second action. One of the key ones, originally not fully supported by LAVA and KernelCI, is the handling of signatures/hashes so we ensure that the main components of the environments (tests, logs, reports, kernels/systems, firmware, etc) are signed so CIP Members can trust the obtained results.
+   * Health-checks (blue): the current health-check needs to be improved in order to guarantee that the correct tests, board, B@D version, system version, etc. are being used during the testing process before sharing the testing results, as a way to guarantee that they are meaningful and, up to certain point, reproducible.
+   * Reporting (pink): the current reports that LAVA and KernelCI produce are designed for the kernel (developer) community. They need to be adapted to the CIP use case, which is more focused on maintenance.
+   * Increase test Coverage (green): once the system is configured, the focus will turn into increasing the test coverage of both, the CIP kernel and the core system.
+   * ELCE 2017 (yellow): ELCE is a major milestone for CIP, so for the CIP Testing project. Some key tasks will be executed during and before the event to promote the usage of B@D and to discuss future steps.
+The current diagram is a modified kanban board that shows the current state of the Testing project at a high level. It will be updated regularly. For a more fine grain analysis, please check [[https://gitlab.com/cip-project/cip-testing/testing/boards|CIP testing management instance at gitlab.com]].
+{{ :civilinfrastructureplatform:cip_testing_project_task_porgress_0_2.jpg?1000|CIP testing high level action plan  }}
+The current goal is to present at ELCE the testing environment working, leaving refinements and non-critical tasks for the weeks after the event. Please take **dates as estimations and early plans, not commitments**.
+You can follow closely the CIP testing project status through the [[https://gitlab.com/cip-project/cip-testing/testing/boards|kanban board]] and the [[ciptestingmanagementjournal|project journal]].
 ===== Board at Desk Delivery processes and practices =====
 Description of the processes and practices involved in the delivery of Board at Desk tools
+==== CIP testing project management processes ====
+=== Bugs management ===
+* Check the CIP testing project [[https://gitlab.com/cip-project/cip-testing/testing/boards/322796?&label_name[]=bug|bugs board]]
 ==== Release process howto ====

Wiki

User Tools

Site Tools

Differences

Page Tools