Automated end-to-end testing

johanstokking commented 4 years ago

Summary

Automated end-to-end testing.

Why do we need this?

Regression testing in CI.

What is already there? What do you see now?

Automated frontend testing: https://github.com/TheThingsNetwork/lorawan-stack/issues/2605
CLI for simulating join-requests and uplink messages

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

rvolosatovs commented 3 years ago

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

rvolosatovs commented 3 years ago

Refs #3606

KrishnaIyer commented 3 years ago

Refs https://github.com/TheThingsIndustries/lorawan-stack/issues/2652

KrishnaIyer commented 3 years ago

This needs to get moving. I've bumped https://github.com/TheThingsNetwork/lorawan-stack/issues/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 commented 3 years ago

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 commented 3 years ago

What is the status here?

KrishnaIyer commented 3 years ago

Replaced by https://github.com/TheThingsIndustries/lorawan-stack/issues/2742

TheThingsNetwork / lorawan-stack