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.

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

Testing: Added first fuzzing tests and fixed one bug (yeah!) #14

Merged
merged 25 commits into from
Oct 17, 2022

Conversation

andygrunwald
Copy link
Owner

Added a few fuzzing tests from https://go.dev/doc/fuzz/

Go v1.18 is required.

Fixed one type assertion bug found by fuzzing.

* main: (36 commits)
  README: Add chapter about development + unit testing
  README: New headline for other parsers and moved inspiration chapter down
  README: Add new (more extensive) example
  ci: run unit tests on Go 1.19-1.15
  ci: run staticcheck only on latest Go version
  ci: run go vet only on latest Go version
  ci: run go fmt only on latest Go version
  testing: Add testcase to expect a curly brace as a second item, not an ident
  Fixed missleading error message: We expect a curly brace as a second token, not an ident
  testing: Add new test for an broken/invalid comment
  parseMap(): Simplified code a bit by removing duplicate statements
  Makefile: Add commands for go test coverage and displaying them as HTML
  Parser/parseMap: Remove handling of CommentDoubleSlash and forgotten debug fmt.Println
  New testdata: Full blown sample configuration file
  Makefile: Fixed staticcheck installation
  Go: Removed v1.17, added v1.19
  Bump actions/cache from 3.0.10 to 3.0.11
  Bump actions/cache from 3.0.8 to 3.0.10
  Bump actions/cache from 3.0.7 to 3.0.8
  Bump actions/cache from 3.0.6 to 3.0.7
  ...
@andygrunwald andygrunwald merged commit 4c7af3c into main Oct 17, 2022
@andygrunwald andygrunwald deleted the fuzzing branch October 17, 2022 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant