Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create tasks that will follow the Documentation instructions #2878

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

gligorisaev
Copy link
Contributor

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

Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Signed-off-by: gligorisaev <gligorisaev@gmail.com>
@gligorisaev gligorisaev requested a review from a team as a code owner May 15, 2024 08:25
@gligorisaev gligorisaev marked this pull request as draft May 15, 2024 08:26
Copy link
Contributor

Robot Results

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

Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Signed-off-by: gligorisaev <gligorisaev@gmail.com>
Raise Alarm With Timestamp Keyword
[Arguments] ${alarm_type} ${text} ${severity} ${timestamp}
${payload}= Set Variable {"text": "${text}", "severity": "${severity}", "time": "${timestamp}"}
Execute Command tedge mqtt pub te/device/main///a/${alarm_type} '{${payload}}' -r -q 2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add a check that the alarm is actually stored in C8Y

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants