Add unit-tests for the Mazevo events parser in parser/mazevoParser.go

Open Beginner friendly
#151 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go
Domain
testing

Research direction

Start with parser/mazevoParser.go and inspect the repository’s existing _test.go files to follow its unit-test structure. Use Go’s built-in testing library to cover the Mazevo events parser, then check test coverage; done means the parser has useful unit tests and the coverage has been reviewed.

Written by the indexing model from the issue text.

Description

L2 Type: Internal

Add unit tests for the mazevo events parser using Go's built-in testing library.

Follow the current structure of the unit-tests, which means a file _test.go is associated with the file of the main code.

Be sure to seek out resources for details on how to write good unit tests if you are unsure. Also make sure to check the coverage of the test because the higher the coverage, the better.

Dominant language
Go
Stars
11
Forks
54
Avg merge
2d 14h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UTDNebula/api-tools

All issues in UTDNebula/api-tools

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.