User Tools

Site Tools


civilinfrastructureplatform:ciptesting

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:ciptesting [2017/10/12 12:30]
rajmarshall [Action 1: Board At Desk - Single Developer (B@D)] add a licence section for contribution guidance
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.
       - 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.
-   * Interested in previous releases of B@D? Please check the [[/​civilinfrastructureplatform/​ciptesting/​releases|CIP Testing Project Releases]] wiki page.+   * 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 === === Contribute to the CIP testing project ===
Line 40: Line 43:
       * 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.+      * 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 80: 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.1507811448.txt.gz · Last modified: 2017/10/12 12:30 by rajmarshall