This Discrepancy Log is to be used for documentation of any discrepancies (e.g. failed test cases, test case errors, testing execution errors) found during testing. These should include all test cases where the result has been set to failed.
-
Clarification: Discrepancies detected during a test run will be documented in the Discrepancy Log (DIL) version associated with the test run. The DIL will be created during each test run. Any updated version of the DIL showing no discrepancies serves as evidence for the successful correction of the error(s) causing the discrepancies.
+
Clarification: Discrepancies detected during a test run will be documented in the Discrepancy Log (DIL) version associated with the test run. The DIL will be created during each test run. Any updated version of the DIL showing no discrepancies serves as evidence for the successful correction of the error(s) causing the discrepancies.
Furthermore, this discrepancy log only covers discrepancies from tasks automated through OpenDevStack. Any manual tasks done outside of OpenDevStack, which created discrepancies, must be covered in a secondary DIL.
- A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
+ A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
A person who creates a PR gets attributed as its author and nominates at least one reviewer. Once mandatory changes requested by the reviewers have been incorporated by the contributors, reviewers can approve the PR. An approval permits that the approved contribution can be merged from a temporary source branch into a longer living target branch inside the repository.{{#if metadata.gxp}} A single person must not assume the roles of contributor and reviewer on the same PR (no self-approvals).{{/if}}
- A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
+ A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
A person who creates a PR gets attributed as its author and nominates at least one reviewer. Once mandatory changes requested by the reviewers have been incorporated by the contributors, reviewers can approve the PR. An approval permits that the approved contribution can be merged from a temporary source branch into a longer living target branch inside the repository.{{#if metadata.gxp}} A single person must not assume the roles of contributor and reviewer on the same PR (no self-approvals).{{/if}}
- A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
+ A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
A person who creates a PR gets attributed as its author and nominates at least one reviewer. Once mandatory changes requested by the reviewers have been incorporated by the contributors, reviewers can approve the PR. An approval permits that the approved contribution can be merged from a temporary source branch into a longer living target branch inside the repository.{{#if metadata.gxp}} A single person must not assume the roles of contributor and reviewer on the same PR (no self-approvals).{{/if}}
- A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
+ A Bitbucket Pull Request (PR) is where contributors and reviewers meet to discuss and assert the readiness of a contribution to a Bitbucket repository comprising code, tests, configuration, or a combination of these.
A person who creates a PR gets attributed as its author and nominates at least one reviewer. Once mandatory changes requested by the reviewers have been incorporated by the contributors, reviewers can approve the PR. An approval permits that the approved contribution can be merged from a temporary source branch into a longer living target branch inside the repository.{{#if metadata.gxp}} A single person must not assume the roles of contributor and reviewer on the same PR (no self-approvals).{{/if}}
This document describes the installation of the software-defined component {{data.repo.id}}. The installation is based on the corresponding Technical Installation Plan (TIP) of Config Item: {{metadata.buildParameter.configItem}}.
+
-
The plan outlines additional chapters, namely Installation Prerequisites (3) and Environmental Conditions (4).
+
Technical Installation Report for '{{ metadata.name }}'
-
Installation plan reference: ITEMS Document Number {{metadata.version}}-{{metadata.jenkins.buildNumber}}, Version: {{metadata.referencedDocs.TIP}}.
Installations steps have been successfully conducted. Overall installation status:
+
+ This document describes the installation of the software-defined
+ component {{ data.repo.id }}. The installation is based on the corresponding Technical
+ Installation Plan (TIP) of Config Item:
+ {{ metadata.buildParameter.configItem }}.
+
-
-
-
Status
-
OK
-
-
+
+ The plan outlines additional chapters, namely
+ Installation Prerequisites (3) and
+ Environmental Conditions (4).
+
-
2.1Jenkins
-
Jenkins Job has been successfully executed:
+
+ Installation plan reference: ITEMS Document Number
+ {{ metadata.version }}-{{ metadata.jenkins.buildNumber }}, Version: {{ metadata.referencedDocs.TIP }}.
+
All deliverables of the Technical Installation Plan have been successfully executed and the signature of this Report verifies that the system has been installed according to all requirements stated in the Installation Plan or, in the event the requirements are not met, that the deviations and/or failures are properly documented and addressed.
+ Wait until all Pods, PVCs, Services, and minimum
+ number of Pods of a Deployment, StatefulSet, or
+ ReplicaSet are in a ready state
+
+
+ Applicable resources are in ready state
+
+
+ Applicable resources are in ready state
+
+
Pass
+
+
+
+ {{/data.repo}}
+
-
5.1Definitions
- {{#if data.sections.sec5s1.show}}
+
+
4Conclusion Statement
+
+ All deliverables of the Technical Installation Plan have been
+ successfully executed and the signature of this Report verifies
+ that the system has been installed according to all requirements
+ stated in the Installation Plan or, in the event the
+ requirements are not met, that the deviations and/or failures
+ are properly documented and addressed.
+
+
+
+
+
5Definitions and Abbreviations
+
+
5.1Definitions
+ {{#if data.sections.sec5s1.show}}
-
{{{data.sections.sec5s1.content}}}
+
+ {{{data.sections.sec5s1.content}}}
+
- {{else}}
+ {{else}}
N/A
- {{/if}}
+ {{/if}}
-
5.2Abbreviations
- {{#if data.sections.sec5s2.show}}
+
5.2Abbreviations
+ {{#if data.sections.sec5s2.show}}
-
{{{data.sections.sec5s2.content}}}
+
+ {{{data.sections.sec5s2.content}}}
+
- {{else}}
+ {{else}}
N/A
- {{/if}}
-
+ {{/if}}
+
-
-
6Reference Documents
-
-
Technical Installation Plan ({{metadata.referencedDocs.TIP}})
-
- {{#if data.sections.sec6.show}}
+
+
6Reference Documents
+
+
+ Technical Installation Plan ({{metadata.referencedDocs.TIP}})
+
+
+ {{#if data.sections.sec6.show}}
-
{{{data.sections.sec6.content}}}
+
+ {{{data.sections.sec6.content}}}
+
- {{/if}}
-
+ {{/if}}
+
-
-
7Document History
- {{#if data.documentHistory}}
-
-
-
Version
-
Date
-
Author
-
Change Reference
-
-
- {{#each data.documentHistory}}
-
-
{{{docVersion}}}
-
See Summary of electronic document or signature page of printout.
-
- {{{rational}}}
-
- {{#each issueType}}
- {{#if added}}
- The following {{type}} were added:
-
- {{#each added}}
-
{{key}}{{#if details}}: {{details}}{{/if}}
+
+
7Document History
+ {{#if data.documentHistory}}
+
+
+
Version
+
Date
+
Author
+
Change Reference
+
+
+ {{#each data.documentHistory}}
+
+
{{{docVersion}}}
+
+ See Summary of electronic document or signature page
+ of printout.
+
+
+ {{{rational}}}
+
+ {{#each issueType}}
+ {{#if added}}
+ The following {{ type }} were added:
+