approvals / approvals/ApprovalTests.LabVIEW
Make it easier to create a new verify in LUnit
Nobody has claimed this yet.
- Dominant language
- LabVIEW
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Either figure out a way to replace the Assert Equals with QuickDrop.
currently Quick Drop Verify.vim ends up with the Verify.vim for VITester. - the qualified name does not show up in QD.
Or
figure out a way to add a Template VI to a newly created LUnit Test. Maybe some plugin function on Anton's Part or maybe when in installing approvals if LUnit is installed, it just finds it and adds it.
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 comparing QuickDrop Verify.vim with the Verify.vim used by VITester, then inspect how a new LUnit Test is created and where Template VI, plugin, or installation approval hooks could apply. Done means a newly created LUnit test receives the correct LUnit verify behavior instead of VITester's Verify.vim.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100