[ 
https://issues.apache.org/jira/browse/BEAM-14440?focusedWorklogId=767939&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767939
 ]

ASF GitHub Bot logged work on BEAM-14440:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/May/22 15:08
            Start Date: 09/May/22 15:08
    Worklog Time Spent: 10m 
      Work Description: jrmccluskey opened a new pull request, #17587:
URL: https://github.com/apache/beam/pull/17587

   Adds a few small fuzz test examples to the coders package, validating that a 
successful Encode() call will be followed by a successful Decode() call and 
then have an output matching the input for strings, ints, bytes, and doubles.
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] [**Choose 
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and 
mention them in a comment (`R: @username`).
    - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue, if applicable. This will automatically link the pull request to the 
issue.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/workflows/Build%20python%20source%20distribution%20and%20wheels/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/workflows/Python%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/workflows/Java%20Tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI.
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 767939)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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)

Reply via email to