civilinfrastructureplatform:ciptesting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:ciptesting [2017/06/14 09:50] Agustin Benito Bethencourt link to the new bug report list |
civilinfrastructureplatform:ciptesting [2018/04/27 13:17] (current) rajmarshall remove irrelevant text |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| - Define kernel testing as a service within CIP: define the testing environment within CIP assuming that in some cases, Members would share the tests, test results and laboratory and in others they will not. | - Define kernel testing as a service within CIP: define the testing environment within CIP assuming that in some cases, Members would share the tests, test results and laboratory and in others they will not. | ||
| - | For more details, please check the [[ciptestingfaq|CIP Testing FAQ]] | + | For more details, please check the [[:civilinfrastructureplatform/ciptestingfaq|CIP Testing FAQ]]. If you are interesting in following up how the project is progressing, please check the [[:civilinfrastructureplatform/ciptesting/management|CIP Testing Project Management page]]. |
| ==== Action 1: Board At Desk - Single Developer (B@D) ==== | ==== Action 1: Board At Desk - Single Developer (B@D) ==== | ||
| - | [[http://www.kernelci.org|kernelci.org]] is one of the most sucessful Open Source testing projects. Its distributed nature improve the possibilities of collaborating among different developers and corporations. Distributed boards farms across the world are working together to test every merge of an upstream Linux kernel tree, detecting bugs and regressions in a timely manner and reporting them back to kernel developers. | + | [[http://www.kernelci.org|kernelci.org]] is one of the most successful Open Source testing projects. Its distributed nature improve the possibilities of collaborating among different developers and corporations. Distributed boards farms across the world are working together to test every merge of an upstream Linux kernel tree, detecting bugs and regressions in a timely manner and reporting them back to kernel developers. |
| Board At Desk - Single Developer, given name for action 1, has as goal to create and publish a VM that contains all the kernelci tools so a single developer can test the CIP kernel (or any other Linux kernel) on a board connected to the user's development machine. This board will initially be the selected hardware platforms for the CIP project which at the moment is Beaglebone Black. Any other board would work too after some basic configuration. {{ :civilinfrastructureplatform:board_at_desk_single_dev_block_diagram_low_quality.jpg?500|Board At Desk - Single Dev. Schema}} | Board At Desk - Single Developer, given name for action 1, has as goal to create and publish a VM that contains all the kernelci tools so a single developer can test the CIP kernel (or any other Linux kernel) on a board connected to the user's development machine. This board will initially be the selected hardware platforms for the CIP project which at the moment is Beaglebone Black. Any other board would work too after some basic configuration. {{ :civilinfrastructureplatform:board_at_desk_single_dev_block_diagram_low_quality.jpg?500|Board At Desk - Single Dev. Schema}} | ||
| Line 27: | Line 27: | ||
| * The wiki pages that will guide you through the process of using B@D are: | * The wiki pages that will guide you through the process of using B@D are: | ||
| - Instructions to deploy and configure B@D, connect the board and try the reference tests. | - Instructions to deploy and configure B@D, connect the board and try the reference tests. | ||
| - | - Deploy B@D through [[ciptestingboardatdeskdingledevdeployment#b-d-deployment-method-2-building-vm-from-scratch-using-vagrant-14|Vagrant]] or by downloading the [[ciptestingboardatdeskdingledevdeployment#b-d-standalone-virtual-machine-box|B@D standalone VM box]] directly. | + | - Deploy B@D through [[ciptestingboardatdeskdingledevdeployment#b-d-deployment-method-2-building-vm-from-scratch-using-vagrant-15|Vagrant]] or by downloading the [[ciptestingboardatdeskdingledevdeployment#b-d-standalone-virtual-machine-box|B@D standalone VM box]] directly. |
| - Once deployed, [[[[ciptestingboardatdesksingledevsetup|configure B@D]]. | - Once deployed, [[[[ciptestingboardatdesksingledevsetup|configure B@D]]. | ||
| - | - Connect the board ([[beagleboneblackboard|Beaglebone Black]] in this case) to the host machine, where B@D is deployed. | + | - Connect the board ([[beagleboneblackboard|Beaglebone Black]] or [[renesasboard|Renesas IWG20M]]) to the host machine, where B@D is deployed. |
| - [[cipsystembuildhowto|Build the kernel (system)]] to be tested and required artefacts. | - [[cipsystembuildhowto|Build the kernel (system)]] to be tested and required artefacts. | ||
| - Check the [[civilinfrastructureplatform/ciptestingreferencetestcases|reference test cases]] and try them as examples. | - Check the [[civilinfrastructureplatform/ciptestingreferencetestcases|reference test cases]] and try them as examples. | ||
| - If you experience any problem following the above instructions, please check the [[ciptestingknownissues|Known Issues and Workarounds]] wiki page before reporting any issue. | - If you experience any problem following the above instructions, please check the [[ciptestingknownissues|Known Issues and Workarounds]] wiki page before reporting any issue. | ||
| - | * Contribute to the CIP testing project | + | * Do you want to know more about the release process followed with the CIP Testing project of tools and code? You should take a look at the following pages then: |
| + | * Check the CIP Testing project [[:civilinfrastructureplatform/ciptesting/management|management wiki page]] to get a description of the process followed and links to other related content. | ||
| + | * Interested in previous releases of B@D? Please check the [[/civilinfrastructureplatform/ciptesting/releases|CIP Testing Project Releases]] wiki page. | ||
| + | * All the marketing related material created for every release is published on the CIP Testing Project [[/civilinfrastructureplatform/ciptesting/batdmarketing|marketing page]]. | ||
| + | |||
| + | === Contribute to the CIP testing project === | ||
| + | |||
| + | If you want to contribute to the CIP Testing project, please consider reading the following information: | ||
| * Check the code at [[https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/tree/master|Gitlab.com]] | * Check the code at [[https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/tree/master|Gitlab.com]] | ||
| * Please read the [[ciptestingfaq|CIP Testing FAQ]] to learn more about B@D. | * Please read the [[ciptestingfaq|CIP Testing FAQ]] to learn more about B@D. | ||
| - | * The delivery process is described in the [[ciptestingmanagement|CIP testing management]] wiki page. | + | * The delivery process is described in the [[/civilinfrastructureplatform/ciptesting/management|CIP testing management]] wiki page. |
| * Join the technical mailing list ([[https://lists.cip-project.org/mailman/listinfo/cip-dev|cip-dev]]) to follow this effort. | * Join the technical mailing list ([[https://lists.cip-project.org/mailman/listinfo/cip-dev|cip-dev]]) to follow this effort. | ||
| * Report a [[https://gitlab.com/cip-project/cip-testing/testing/boards/322796?&label_name[]=bug|bug]]. | * Report a [[https://gitlab.com/cip-project/cip-testing/testing/boards/322796?&label_name[]=bug|bug]]. | ||
| + | * Any contributions for the CIP Testing project need to have licences that are compatible with the existing licences (APGL-3.0), source files must have a licence header and any repositories must have a LICENSE file and a LICENSE.spdx file - see the current repositories for style and see also [[https://commonsconservancy.org/faq/licenseinfo/|the commons conservancy]] guidance. | ||
| ==== Action 2: CIP kernel testing ==== | ==== Action 2: CIP kernel testing ==== | ||
| Line 75: | Line 83: | ||
| CIP is not just about the kernel. The goal is to create a base system for the industry. In order to achieve the general goal, this initiative will require more of a journey than the one taken for the kernel, but for a base/core system. | CIP is not just about the kernel. The goal is to create a base system for the industry. In order to achieve the general goal, this initiative will require more of a journey than the one taken for the kernel, but for a base/core system. | ||
| - | ==== Action 5: Define kernel testing as a service within CIP ==== | + | ==== Action 5: Define kernel/system testing as a semi-distributed service within CIP ==== |
| Once CIP develops a testing culture, it will be time for scaling up the testing activities by turning the project into a service for Members and CIP friends, in collaboration with the kernel community. | Once CIP develops a testing culture, it will be time for scaling up the testing activities by turning the project into a service for Members and CIP friends, in collaboration with the kernel community. | ||
| [[start|Back to the parent page]] | [[start|Back to the parent page]] | ||
civilinfrastructureplatform/ciptesting.1497433812.txt.gz · Last modified: 2017/06/14 09:50 by Agustin Benito Bethencourt
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
