Tests: version number checks need hint to tester

[martinwork]

In https://github.com/bbcmicrobit/PythonEditor/blob/master/tests/manual/test-procedure.rst

Test Case: Help menu expands and links work '''''''''''''''''''''''''''''''''''''''''''

• Click the "Help" button.
• [X] Confirm help drop down menu appears.
• [X] Confirm the correct "Editor Version" is displayed.
• [1] Confirm the correct "MicroPython Version" is displayed.

Need hints to the tester about where to find the version numbers to check against.

[microbit-carlos]

You are right, but I think ultimately, based on how we end up running this checklist there isn't a definitive way to know.

• If we are running from this repository master branch, then it would probably be whatever is the latest GitHub release (but we could have pre-releases from a beta branch and those could also be in that list)
• If we are running from a branch, it could be anything, depending on how the branch is being develop
• If we are running the tests before a release, then version string might have been updated already or not, as usually we want to do that on the last commit before tagging, but sometimes we have to tag and start deployment while the tests are being run
• etc

So I think this is probably a judgment call, based on the state of the Editor and MicroPython at the time of the test run. The editor will ultimate show this, which is manually updated: https://github.com/bbcmicrobit/PythonEditor/blob/604de68cdd00284568c1f52e43ad23cf5c8c8f19/editor.html#L81-L82

Maybe we need to add as a pre-requisit to list the expected Python Editor version, MicroPython version, we could expand it as well to indicate what commit from what repo it is being tested. Would that help?

[microbit-carlos]

Unfortunately I think we'll leave this "unresolved" as a judgement call for the tester. Thanks for the report Martin, sorry I didn't find an easy way to clarify it.