CONTRIBUTING.md needs more information on how to run tests

[gearama]

I ran cargo test on a clean clone after cargo build

 Running tests\consumer.rs (target\debug\deps\consumer-943bfee5a1400f15.exe)

running 7 tests
test receive_lots_of_events ... FAILED
test test_get_properties ... FAILED
test test_new ... FAILED
test test_new_with_error ... FAILED
test test_get_partition_properties ... FAILED
test test_close ... FAILED
test test_open ... FAILED

I know the section says needs work but we really should have instructions on how to run tests if they require extra setup, also the base unit tests should maybe run the first time at least without failures.

Either specify what the tests require before testing or not have them run, or run a setup portion to get everything in order.

As a customer, seeing this from a basic clone and test seems off-putting

Got the same results when running Test-Pacjkages.ps1 from the eng folder

[hallipr]

When I run cargo test from repo root in a fresh clone, most tests pass. Event Hubs appears to skip tests when prereqs aren't available while Key Vault tests fail for missing test-proxy.

[heaths]

We'll acquire test-proxy automatically with #1955. It's lower on the priority list, though. @LarryOsterman why are Event Hubs tests failing by default? They don't even use test-proxy nor should they be running unless @gearama has AZURE_TEST_MODE set at her machine (or parent process, otherwise) scope.

[LarryOsterman]

Eventhubs test should pass (or be skipped) if AZURE_TEST_MODE isn't set, or if it's set to anything other than "live".

They do when I run them locally (modulo doctest failures that are related to local changes).

My strong guess is that AZURE_TEST_MODE was set in George's environment.

[LarryOsterman]

Confirmed with @gearama that AZURE_TEST_MODE was set in his environment, which explains the failure.