-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add CLI tests for jabref #14129
Copy link
Copy link
Closed
Labels
component: JabKit [cli]dev: code-qualityIssues related to code or architecture decisionsIssues related to code or architecture decisionsdev: testingRelated to testsRelated to testsgood second issueIssues that involve a tour of two or three interweaved components in JabRefIssues that involve a tour of two or three interweaved components in JabRef
Description
Metadata
Metadata
Assignees
Labels
component: JabKit [cli]dev: code-qualityIssues related to code or architecture decisionsIssues related to code or architecture decisionsdev: testingRelated to testsRelated to testsgood second issueIssues that involve a tour of two or three interweaved components in JabRefIssues that involve a tour of two or three interweaved components in JabRef
Type
Fields
Give feedbackNo fields configured for feature.
Projects
StatusShow more project fields
Done
Is your suggestion for improvement related to a problem? Please describe.
Currently there is almost no testing for the actual CLI functionality, this caused
jabref pseudonymizeto have some easy to solve bugs that should have been caught by testing.Describe the solution you'd like
There is already a test for
ArgumentProcessorI propose we introduce tests similar to those forArgumentProcessorfor the ten other classes present. Additionally, we can create some abstraction that makes creating tests for the CLI more developer friendly.