Add tests for devmode timestamps

[algochoi]

Adds tests for get/setting timestamp offsets in dev mode. Only confirms that the algod request/response is correct as a sanity check.

Example here: algorand/py-algorand-sdk#468

[tzaffi]

Is line 9 purely testing GET /v2/devmode/blocks/offset/ ? If so, maybe it's also worth adding a step that calls GET v2/block/{round} and verifies that the offset had the desired effect? Might be tricky to make it non-flaky though...

[tzaffi]

Looks good. Just proposing an additional step (or two)

[winder]

I don't think an integration test adds much safety here beyond whats already been done in the algod tests.

What do you think about adding the path/response unit tests and calling it a day?

For example: https://github.com/algorand/algorand-sdk-testing/pull/245/files

[tzaffi]

I don't think an integration test adds much safety here beyond whats already been done in the algod tests.

What do you think about adding the path/response unit tests and calling it a day?

For example: https://github.com/algorand/algorand-sdk-testing/pull/245/files

I think some kind of E2E in go-algorand or integration test in one repo ought to exist showing that the devmode timestamps are behaving as expected. Maybe this already exists, but I didn't spot such a test in a brief search. Maybe add this test somewhere in this file?

[algochoi]

Alternatively we could implement a full end to end test for devmode APIs for only one SDK (e.g. Python) under the @devmode integration tag and the rest can be tested with the path unit test?

[algochoi]

What do you think about adding the path/response unit tests and calling it a day?

Added path/response tests here: #276

[winder]

Based on our previous conversations, I think this can be closed. Let me know if you disagree and we can discuss in person.

[algochoi]

Sounds good, I'll close this for now.