Feat: Custom Assertions
Nobody has claimed this yet.
- Dominant language
- Apex
- Stars
- 110
- Forks
- 15
- Avg merge
- 1m
- Merged PRs (30d)
- 7
Description
Summary
As a developer, I'd appreciate having some fine grained custom asserts that are baked into the Assert class so that I can do things like Assert.isAccount(obj, friendly message) or Assert.caseCreated() etc.
Suggested Solution
shadow the Assert class - ie: create an Assert Class that contains passthrough methods calling System.Assert.* as well as our custom methods.
Alternative Solutions
Bug the Apex team to allow us to extend Assert.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's proposed Assert class design and the existing System.Assert usage in the repository. Define the initial custom assertion scope and determine how completion would be verified, since the issue does not name files, tests, or a fixed set of assertions.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100