action #1281


Dashboard to integrate external tests

Added by aplanas about 10 years ago. Updated almost 6 years ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:


The basic openQA service allow users to see current results in a read-only way: they can't rearrange or relaunch tests, for example.

But the computer capabilities of the public server are limited, and if the amount of application tests grow up (because there are contributors designing and deploying these tests), maybe we can't run all the tests.

With the dashboard we want to implement a way where a contributor can run a local openQA instance for a specific build, and publish and integrate the result report in the public server, where the rest of the community can see the full results.

Actions #1

Updated by ancorgs almost 10 years ago

  • Target version set to future
Actions #2

Updated by coolo over 9 years ago

  • Category set to 140

I'm not so sure this is still valid.

Actions #3

Updated by aplanas over 9 years ago

Not as is described. But we need something like that if we have remote workers.

Actions #4

Updated by coolo over 8 years ago

  • Status changed from New to Closed

closed for future

Actions #5

Updated by okurz about 8 years ago

when you say "closed for future", how do you know this ticket still exists? shouldn't it be open but just assigned to "future improvements"?

Actions #6

Updated by coolo about 8 years ago

I closed all "future improvements" to be reopened when we are in that future without other problems.

Actions #7

Updated by okurz about 8 years ago

Judging from my experience with project management and planning by software developers I assume this "future" will be … never.

Actions #8

Updated by okurz almost 6 years ago

  • Target version changed from future to future

Also available in: Atom PDF