Page Comparison

...

1. When starting work on a new task/feature the IKEs will create a working branch (named after the Jira IKP ticket) branched from the correct Platform Integration Branch (PIB)
2. IKEs develop code and commit/push their code to the working branch
3. Once the code is ready for prime time, the IKEs will open a pull request from their working branch to the correct PIB
4. When the pull request is created, Bitbucket will trigger an automatic job (on Jenkins) that runs IND integration tests:
   1. If any of the integration tests fails, the pull request will be blocked and merge will not be allowed until code is committed (and pushed to the working branch) to fix the broken tests
   2. When all tests pass, merge will be allowed

FAQ:

• Q: How do I create test cases? 
  A: Please see Indeni knowledge reformed directory structure below. 
  In short - you can use command-runner passing ind script and input file to generate test case
• Q: How many test cases should I have?A: It is recommended to have multiple test cases including negative testing if applicable.
• Q: Can I run test locally before I create PR to ensure that they will pass once PR is created?
  A: Yes! You can use command-runner to run test case, Please refer to Indeni knowledge reformed directory structure below.
• Q: How can I see the test results
  A: Click the link in the upper right of the PR:
  
  
• If the tests fail, and for some reason I want to restart the CI test run, how do I do that?
  Make a comment in the PR with the text "test this please".
• Q: What else this (cool) Continuous Integration can/will do?
  A: We are planning to add more validity checks in the near futures such as:

...