Decision inputs
Facts that change the policy answer
Here the tool receives a function, expected behaviour and existing test conventions, while someone ultimately relies on new unit-test cases. The policy must evaluate the whole path between them.
- 1Task and owner
- Software engineer wants to generate unit tests. The policy check should identify who can approve, correct or withdraw new unit-test cases.
- 2Information involved
- A function, expected behaviour and existing test conventions. Include attachments and connected sources when deciding the highest information classification.
- 3Tool and account
- An approved company account. The request should identify the exact account because product-level approval leaves important controls unknown.
- 4Intended result
- The expected result is new unit-test cases. Record the audience and the next system in the chain, rather than describing the output only as a draft.
- 5Consequence if it is wrong
- Generated tests can merely mirror the implementation and miss the actual requirement. A familiar task still needs escalation when this consequence becomes plausible.
- 6Human review
- engineer responsible for the feature should inspect, change, reject or stop the result. Make the review happen before reliance and give the reviewer a real way to stop the work.
Possible policy routes
The task name alone cannot decide it.
A published workplace policy can return different answers for the same task. These are the practical branches worth encoding.
A routine policy route may be possible
The lower-friction route begins when the exact account is approved, only the minimum proprietary source code is used, new unit-test cases remains within the stated purpose, and engineer responsible for the feature reviews it before use.
Approval may be required
Send the request for approval if the account or data handling is uncertain, generated tests can merely mirror the implementation and miss the actual requirement, or new unit-test cases reaches people or systems beyond the requester’s authority.
The request may need to stop or change
The proposed use should pause if restricted information would enter an unapproved service, the output would act before engineer responsible for the feature can intervene, or derive expected cases from requirements and run the complete test suite cannot be maintained. Consider less information, a controlled account or a non-AI process.
Request checklist
Questions to ask before using the tool
- 01
Is the exact account approved for generate unit tests, including its plug-ins and connected sources?
- 02
What is the most sensitive element in a function, expected behaviour and existing test conventions, and does the tool need it?
- 03
Does new unit-test cases create an external statement, a decision or an automated action?
- 04
Who replaces engineer responsible for the feature when the request falls outside ordinary expertise?
- 05
Is this genuinely one request, or will repeated use turn it into an embedded process?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- software engineer
- task
- Use AI to generate unit tests.
- information
- a function, expected behaviour and existing test conventions
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Draft or analyse
- impact
- Internal work
- review
- Complete human review
- owner
- engineer responsible for the feature
Useful safeguards
Controls that fit this request
- ✓
Derive expected cases from requirements and run the complete test suite
- ✓
Start with a de-identified sample of a function, expected behaviour and existing test conventions before considering broader access.
- ✓
Treat a new purpose, region, data source or recipient as a new request rather than silently extending this one.
- ✓
Record the request and reviewer without copying unnecessary parts of a function, expected behaviour and existing test conventions into the audit trail.
Questions people ask
About this AI use
Is using AI to generate unit tests automatically allowed?
The task name cannot settle the answer. Apply the company’s published rules to a function, expected behaviour and existing test conventions, the exact account, new unit-test cases, its audience and the proposed review.
Which facts should be submitted before work begins?
Describe new unit-test cases, identify a function, expected behaviour and existing test conventions, name the exact tool and account, explain who will receive or rely on the output, and state how engineer responsible for the feature will review it.
What belongs in the completed policy record?
Record the request and reviewer without copying unnecessary parts of a function, expected behaviour and existing test conventions into the audit trail. A classification and controlled reference may be enough when copying a function, expected behaviour and existing test conventions would create unnecessary risk.