Create tasks that will follow the Documentation instructions

[gligorisaev]

Proposed changes

For documentation checking purposes I am creating collection of End to End tasks which will follow the descriptions/instructions from thinedge documentation.
These tasks are running on an Raspberry PI.
The idea behind is that as soon as some task fail that would mean that changes in the documentations are needed or some regression mailfunction has been detected.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
433	0	3	433	100	58m56.358857s

[reubenmiller]

Duplicated line.

Suggested change

	Should Contain ${OUTPUT} tedge - CLI tool use to control and configure thin-edge.io
	Should Contain ${OUTPUT} tedge - CLI tool use to control and configure thin-edge.io
	Should Contain ${OUTPUT} tedge - CLI tool use to control and configure thin-edge.io

[reubenmiller]

This should be deleted

[reubenmiller]

It would make more sense to make this a Keyword (function) that takes an argument for the type, then you can reuse it for the other measurements.

Verify Measurement In Cumulocity
    [Arguments]        ${type}
    Device Should Have Measurements    type=${type}    minimum=1    maximum=1

Then the usage is just:

Verify Measurement In Cumulocity    type=environment

[reubenmiller]

Suggested change

	#Not verifiing this test step because the test running in container already exists: tests/RobotFramework/tests/installation/install_on_linux.robot
	#Skip verification step as system tests already exist: tests/RobotFramework/tests/installation/install_on_linux.robot

[reubenmiller]

Suggested change

	#Not verifiing this test step because the test running in container already exists: tests/RobotFramework/tests/installation/install_on_linux.robot
	#Skip verification step as system tests already exist: tests/RobotFramework/tests/installation/install_on_linux.robot

[reubenmiller]

Now you can use the same Verify Measurement In Cumulocity keyword to verify that this message is also published.

[reubenmiller]

We shouldn't be using /home/pi path...use some other path like:

Suggested change

	${log} Transfer To Device target/aarch64-unknown-linux-musl/packages/*.deb /home/pi/
	${log} Transfer To Device target/aarch64-unknown-linux-musl/packages/*.deb /var/local/share/

[reubenmiller]

We shouldn't be using /home/pi path...use some other path like:

Suggested change

	${log} Transfer To Device target/armv7-unknown-linux-musleabihf/packages/*.deb /home/pi/
	${log} Transfer To Device target/armv7-unknown-linux-musleabihf/packages/*.deb /var/local/share/

[reubenmiller]

Suggested change

	Transfer To Device ${CURDIR}/uninstall-thin-edge_io.sh /home/pi/uninstall-thin-edge_io.sh
	Transfer To Device ${CURDIR}/uninstall-thin-edge_io.sh /var/local/share/uninstall-thin-edge_io.sh

[reubenmiller]

Though there are other places which also use the /home/pi folder...best to avoid this all together.

[reubenmiller]

This assumes you are running on a specific architecture, e.g. aarch64, so you'll need to the same arch detecting logic.

[reubenmiller]

This won't work as expected, as the shell wildcard is within the double quotes, meaning it will not be expanded to folders with tedge_* in the name.

Suggested change

	sudo rm -rf "$path/tedge_*"
	sudo rm -rf "$path/tedge_"*

[reubenmiller]

@gligorisaev What is the state of this PR, it seems to be still a work-in-progress. In that case it would be better to set it to the Draft state. It is unclear which comments have been addressed or not as there aren't any links to the commits which address the comments.