civilinfrastructureplatform:ciptesting:centalisedtesting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
civilinfrastructureplatform:ciptesting:centalisedtesting [2020/04/21 10:05] patersonc |
civilinfrastructureplatform:ciptesting:centalisedtesting [2023/12/18 12:18] swvanbuuren Add section on SQUAD test reporting |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The second goal for CIP testing was to centralise testing so that developers can run tests without having local access to a platform. This is becoming more and more useful for CIP as the list of [[civilinfrastructureplatform:ciptesting:cipreferencehardware|reference platforms]] grows. It also means that tests can be triggered and run automatically 24/7. | The second goal for CIP testing was to centralise testing so that developers can run tests without having local access to a platform. This is becoming more and more useful for CIP as the list of [[civilinfrastructureplatform:ciptesting:cipreferencehardware|reference platforms]] grows. It also means that tests can be triggered and run automatically 24/7. | ||
| - | The third goal for CIP testing is to set up Continuous Integration (CI) testing to automatically test CIP software on CIP hardware. See the [[civilinfrastructureplatform:ciptesting:centalisedtesting:cioverview|Continuous Integration testing overview]] page for more details. | + | The third goal for CIP testing was to set up Continuous Integration (CI) testing to automatically test CIP software on CIP hardware. See the [[civilinfrastructureplatform:ciptesting:centalisedtesting:cioverview|Continuous Integration testing overview]] page for more details. |
| + | |||
| + | The fourth goal for CIP testing is to integrate with the [[https://kernelci.org/|KernelCI project]]. This work is underway and the latest results can be viewed at [[https://kernelci.ciplatform.org/|kernelci.ciplatform.org]]. | ||
| ===== CIP Testing Architecture ===== | ===== CIP Testing Architecture ===== | ||
| The block diagram below provides an overview of CIP's centralised test infrastructure. | The block diagram below provides an overview of CIP's centralised test infrastructure. | ||
| Line 64: | Line 66: | ||
| LAVA can also email any email address specified in the job description. | LAVA can also email any email address specified in the job description. | ||
| + | |||
| + | == SQUAD == | ||
| + | |||
| + | For detailed test reporting CIP uses the Software Quality Dashboard (SQUAD). Build success and test results are reported to the [[https://squad.ciplatform.org/|CIP SQUAD instance]]. | ||
| === Links === | === Links === | ||
civilinfrastructureplatform/ciptesting/centalisedtesting.txt · Last modified: 2023/12/19 08:55 by swvanbuuren
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
