What was agreed
The objective, scope and criteria the change had to satisfy.
Delivery and traceability
Deliveries in GitHub and GitLab
Receive a pull or merge request with the code change, its requirement and test evidence. Your team assesses the delivered software and decides whether to merge.
Traceability
From approved criteria to the delivered version
- 01
Approved scope
Required outcomes and the rules the change must meet.
- 02
Change review
Implementation checked against those criteria and project rules.
- 03
Tests on that version
QA results and evidence linked to the reviewed code.
- 04
Delivery verification
Changes ready for your team’s assessment and merge decision.
The evidence accompanying a delivery corresponds to the software your team receives.
Visibility
Information for deciding the merge
What was corrected
Recorded findings and attempts let your team inspect how the outcome was reached.
What was verified
Results and a test report linked to the code prepared for delivery.
Code in your repositories
Changes are delivered in your organization's repositories. DevSense does not merge: it prepares the pull or merge request and records the merge when your team performs it.
Depending on project configuration, the pull or merge request opens automatically or through a team action.
- Change description and link to its requirement.
- Test report and results for assessing integration.
- Approved specifications, acceptance criteria and decision history belong to you and can be exported.
Evaluate DevSense in your organization
Review the platform with a representative project and agreed acceptance criteria.