Dawid Rusnak

Hi @iArcadeRob, unfortunately it looks like this repository is no longer maintained - due to that fact I would suggest forking this repository and applying these changes (so nobody will...

Looks like the browser history is applied correctly, so "Back" button goes back to the test suite execution. The actual problem I see is that the links to tests are...

Do we need to have a pod name for execution logs? The execution could have the list of pods used (pre-run, execution, post-run), as only one pod would be running...

Any kind of command. As an example, `testkube run test example-test` to schedule a test from within Kubernetes cluster.

@tkonieczny, is it done? I see that it's marked as done on **Testkube Quality** project, but it's not done in **Testkube**, nor the issue is closed.

Looks like it was marked as Done in Testkube v1.3 project, @vsukhin - is there still some discussion expected?

Looks like it was marked as Done in Testkube v1.4 project, so closing.

@tkonieczny, given that we will support now Cypress 12 instead, should this issue be closed?

@exu, is it still relevant?

We no longer support the [**Dashboard in the OSS version**](https://testkube.io/blog/testkube-dashboard-announcement), so I think that it's obsolete, if that's FE problem. @TheBrunoLopes, @tkonieczny?