[
https://issues.apache.org/jira/browse/BEAM-14440?focusedWorklogId=767971&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767971
]
ASF GitHub Bot logged work on BEAM-14440:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/May/22 15:38
Start Date: 09/May/22 15:38
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #17587:
URL: https://github.com/apache/beam/pull/17587#issuecomment-1121263312
Assigning reviewers. If you would like to opt out of this review, comment
`assign to next reviewer`:
R: @damccorm for label go.
Available commands:
- `stop reviewer notifications` - opt out of the automated review tooling
- `remind me after tests pass` - tag the comment author after tests pass
- `waiting on author` - shift the attention set back to the author (any
comment or push by the author will return the attention set to the reviewers)
The PR bot will only process comments in the main thread (not review
comments).
Issue Time Tracking
-------------------
Worklog Id: (was: 767971)
Time Spent: 40m (was: 0.5h)
> Add coder fuzz tests to the Go SDK
> ----------------------------------
>
> Key: BEAM-14440
> URL: https://issues.apache.org/jira/browse/BEAM-14440
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Jack McCluskey
> Assignee: Jack McCluskey
> Priority: P3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With the Go SDK now on minimum Go version 1.18, fuzz tests can be added to
> the test corpus. The coder package is a good place to start with this, as we
> handle primitives that can be directly generated by Go's native fuzz testing
> and can check that we are getting the same values out after encoding and
> decoding.
>
> An overview of potential fuzz testing in the Beam Go SDK can be found here:
> https://docs.google.com/document/d/1VHe5xFHjsmgOj2upH2k4zT90S5SCPtGYSJNcvPj5fig/edit?usp=sharing
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
