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

Automated end-to-end testing #3202

Closed
johanstokking opened this issue Sep 9, 2020 · 7 comments
Closed

Automated end-to-end testing #3202

johanstokking opened this issue Sep 9, 2020 · 7 comments
Assignees
Labels
needs/discussion We need to discuss this needs/expertise This needs input from an expert tooling Development tooling
Milestone

Comments

@johanstokking
Copy link
Member

Summary

Automated end-to-end testing.

Why do we need this?

Regression testing in CI.

What is already there? What do you see now?

What is missing? What do you want to see?

Scripting common use cases, i.e. creating a gateway, application and device in the Console, sending a simulated join-request via CLI, asserting events displayed in Console, scheduling downlink message, asserting that the downlink message arrives as response to a simulated uplink message via CLI, etc.

Environment

CI

How do you propose to implement this?

Not sure, please provide input

How do you propose to test this?

CI

Can you do this yourself and submit a Pull Request?

No

@johanstokking johanstokking added needs/discussion We need to discuss this tooling Development tooling needs/expertise This needs input from an expert labels Sep 9, 2020
@johanstokking johanstokking added this to the Backlog milestone Sep 9, 2020
@bafonins bafonins modified the milestones: Backlog, Next Up Dec 8, 2020
@rvolosatovs
Copy link
Contributor

Adding me and @KrishnaIyer as we discussed this on last sync

@rvolosatovs
Copy link
Contributor

Refs #3606

@KrishnaIyer
Copy link
Member

@KrishnaIyer KrishnaIyer modified the milestones: Next Up, v3.13.0, 2021 Q2 Mar 31, 2021
@KrishnaIyer
Copy link
Member

KrishnaIyer commented Mar 31, 2021

This needs to get moving. I've bumped #3202 to v3.12.1. I'll do the necessary groundwork and list the results here.

I'll then create issues per function and assign members from this list so we can make some progress.

@kschiffer
Copy link
Contributor

Key issue to move on with this is this one: #3611 

I started working on that already but had to stop for other issues.

@johanstokking
Copy link
Member Author

What is the status here?

@KrishnaIyer
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs/discussion We need to discuss this needs/expertise This needs input from an expert tooling Development tooling
Projects
None yet
Development

No branches or pull requests

6 participants