Documentation error: [verifier service]()

[basictheprogram]

There's a broken link in the ReadMe.md and I don't know where to point the link.

There are a couple of difference between the [verifier service]() and this environment.

[jpluimers]

Right now it still points to https://github.com/chocolatey-community/chocolatey-test-environment/blob/master which is the base URL for anything in the master branch of chocolatey-test-environment itself.

I assume (yes, I know making assumptions is dangerous) that @ferventcoder forgot to add the actual URL in commit bd7d8ab#diff-f9e9432b3b778c13806aea6c01e507d0R57 given the [verifier service]() fragment in https://raw.githubusercontent.com/chocolatey-community/chocolatey-test-environment/master/ReadMe.md

Googling for "verifier service" "chocolatey" makes me find these links that have quite thin content, but seem more or less relevant:

• Moderation: Definitions

  • the verifier - The package verifier service checks the correctness (that the package actually works), that it installs and uninstalls correctly, has the right dependencies to ensure it is installed properly and can be installed silently. The verifier runs against both submitted packages and existing packages (checking every two weeks that a package can still install and sending notice when it fails). We like to think of the verifier as integration testing. It's testing all the parts and ensuring everything is good.

  I wish it would tell about any possibility (and if so: how) to manually submit things for verification.

• https://github.com/chocolatey/package-verifier

  Windows service to verify packages submitted to the community feed (https://chocolatey.org)

  I wish that talked in more detail how to access the instance used to do the "every two weeks" verification.

Reason I came here in the first place is that - though I am totally new to chocolatey development - I want to modify the Oracle SQL Developer package (chocolatey-community/chocolatey-package-requests#383) and do a quick test, but finding my way around has been a challenge.

Create Packages: Build Your Package points to Chocolatey Verifier Testing as a prerequisite, which then requires a Vagrant stack.

Maybe I am missing some simple links to more guidance here, so I am happy to add some pull requests to places where they could be added: just point me to better links and I will try submit some pull requests here and there.