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/10/16 15:59] Agustin Benito Bethencourt [Action 1: Board At Desk - Single Developer (B@D)] |
civilinfrastructureplatform:ciptesting [2018/04/27 13:17] (current) rajmarshall remove irrelevant text |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| - 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. | - 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. | ||
| Line 83: | 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.1508169553.txt.gz ยท Last modified: 2017/10/16 15:59 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
