Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unit testing Stetl #40

Open
fsteggink opened this issue Jul 4, 2016 · 2 comments
Open

Unit testing Stetl #40

fsteggink opened this issue Jul 4, 2016 · 2 comments

Comments

@fsteggink
Copy link
Collaborator

fsteggink commented Jul 4, 2016 •
edited
Loading

Provide Stetl with good unit test coverage.
Also see nlextract/NLExtract#193
@fsteggink fsteggink mentioned this issue Jul 4, 2016
Open
@fsteggink
Copy link
Collaborator Author

Several unit tests were implemented in pull requests #44 and #46. Coverage is now 36%.

@fsteggink
Copy link
Collaborator Author

fsteggink commented Aug 5, 2016 •
edited
Loading

The actual coverage turned out to be lower, since I didn't exclude the tests directory. Solved now in commit 194e780. Part of pull requests #48, including a few more unit tests.

justb4 added a commit that referenced this issue Aug 7, 2016
@justb4
#40 add PacketBuffer Filter and Component-instance-lookup in Chain to…
16e9646 
… help Unit test result inspection/assertions
@justb4 justb4 mentioned this issue Aug 7, 2016
Open
@justb4 justb4 mentioned this issue Feb 27, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fsteggink