Add unit tests from the original repository

- Currently the tests has a package reference to the NuGet release, so can't be used to test local code as of right now.

Author: sondreb

.github/workflows/build.yaml

@@ -31,7 +31,7 @@ jobs:
     - name: Variables
       run: |
         ROCKSDBVNUM=`cat rocksdbversion`
-        echo "ROCKSDBVERSION=$(cat rocksdbversion).2" >> $GITHUB_ENV
+        echo "ROCKSDBVERSION=$(cat rocksdbversion).$(cat revision)" >> $GITHUB_ENV
         echo "ROCKSDBVERSIONBASE=$(cat rocksdbversion)" >> $GITHUB_ENV
       shell: bash
 

README.md

@@ -59,7 +59,11 @@ The version of the NuGet package is set to follow the official RocksDB version,
 
 This will install the managed library and the correct version of the unmanaged library depending on your operating system. The native 64-bit library is automatically built for each official RocksDB release, for Windows, Linux and MacOS, and is included in the package by default.
 
-### Background
+## Releases
+
+To make a new release, edit the "revision" file and commit to trigger a build that will produce a new release. Download the release artefact, verify locally, then publish the release, which will automatically publish to NuGet.org.
+
+## Background
 
 This library is based upon a fork of the original work by [warrenfalk](https://github.com/warrenfalk) and [theolivenbaum](https://github.com/theolivenbaum)
 
@@ -69,6 +73,6 @@ https://github.com/warrenfalk/rocksdb-sharp
 
 https://github.com/curiosity-ai/rocksdb-sharp
 
-### License
+## License
 
 [BSD 2-Clause License](LICENSE)

revision

@@ -0,0 +1 @@
+3

tests/README.md

@@ -0,0 +1,4 @@
+# Testing
+
+As of right now, these tests relies on the NuGet published package. That means you can't test your changes if you are doing any 
+changes to the code generation scripts and  templates.