Merge pull request #149 from MarvinJWendt/generics-refactor

.github/workflows/ci.yml

@@ -14,7 +14,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v2
         with:
-          go-version: 1.16
+          go-version: 1.18
       - name: Run CI
         run: |
           go get

.github/workflows/go.yml

@@ -13,7 +13,7 @@ jobs:
     strategy:
       matrix:
         os: [ ubuntu-latest, windows-latest, macos-latest ]
-        go: [1.15, 1.18]
+        go: [1.18]
     steps:
       - name: Set up Go ${{ matrix.go }}
         uses: actions/setup-go@v2

.github/workflows/golangci.yml → .github/workflows/golangci.yml.bak

@@ -10,10 +10,9 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v2
         with:
-          go-version: 1.16
+          go-version: 1.18
 
       - name: golangci-lint
         uses: golangci/golangci-lint-action@v3
         with:
-          # Required: the version of golangci-lint is required and must be specified without patch version: we always use the latest patch version.
-          version: v1.39
+          version: latest

CONTRIBUTING.md

@@ -7,7 +7,7 @@ This guide will explain how you can contribute to testza.
 Every function in testza follows a specific name scheme.
 As you can see in the [documentations Table of Contents](https://github.com/MarvinJWendt/testza#documentation), testza has many different modules.
 The first word of a new function, is always the module name (eg. `Assert`, `Capture`, `Snapshot`, etc.).
-If the function is inside a nested sub-module, the module names will be chained as in `FuzzInputBool`.
+If the function is inside a nested sub-module, the module names will be chained as in `FuzzBool`.
 The last word of the function name is the actual function name itself.
 
 ### Example
@@ -18,7 +18,7 @@ The last word of the function name is the actual function name itself.
   |   |   ┌ Fuzz integer inputs
   |   |   |   ┌ Full set of integer input fuzzing
   |   |   |   |
-FuzzInputIntFull()
+FuzzIntFull()
 ```
 
 ## File Naming