tests: add overview projects section tests

[HuntTheSun]

Hi,

I am not finished with this, but I have a question:
Do you plan on using the same .db for the demo dashboard and the tests dashboard?

[timdegroot1996]

Hi, cool to see you're working on the tests!

Those are 15 runs that are pretty reusable and also have logs so that has been the easiest for now.
With the demo I assume you mean the example_dashboard.html that I host externally right? (https://timdegroot1996.github.io/robotframework-dashboard/example/robot_dashboard.html)
Because then yeah I use those as input as well.

The latest update I did for the demo was to use this script for generating it to also have some versions:

robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002134.xml:prod:project_1 --projectversion 0.1
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002151.xml:dev:project_2 --projectversion 0.1
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002222.xml:prod:project_1 --projectversion 0.1
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002257.xml:dev:project_2 --projectversion 0.1
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002338.xml:prod:project_1 --projectversion 1.1
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002400.xml:dev:project_2 --projectversion 1.2
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002431.xml:prod:project_1 --projectversion 1.2
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002457.xml:dev:project_2 --projectversion 1.2
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002528.xml:prod:project_1 --projectversion 2.0
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002549.xml:dev:project_2 --projectversion 2.3
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002636.xml:prod:project_1 --projectversion 2.3
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002703.xml:dev:project_2 --projectversion 2.3
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002739.xml:prod:project_1
robotdashboard -g -l -o .\atest\resources\outputs\output-20250313-002915.xml:prod:project_1 --projectversion 2.0
robotdashboard -n robot_dashboard -o .\atest\resources\outputs\output-20250313-003006.xml:prod:project_1 --uselogs

For testing I just generate what is needed (but maybe those commands might need some work).

[HuntTheSun]

Hi, thank you for the quick response!
I made the error of using the IDs and present versions from the demo dashboard for the tests, that's why I ask, I wanted to prevent writing the tests for the wrong dashboard version (again) in case you switched.

[timdegroot1996]

Ah wait let me be a bit clearer then. I use them as inputs so the data is the same. But the loading of the data is handled here. So I basically create the same "simple" dashboard for all runs. It does have 1 project_ tag, but no versions as you can see.

That's why I think that might need changing for the version tests. Or in general it's not a bad idea to update this code to generate the dashboard with a couple of versions.

Now it's hitting me why multiple version additions in one line would be useful 😄 ([this comment] (#136 (comment))), and the script above outline the current benefit quite clearly.

[HuntTheSun]

Good morning,

so if I understand correctly, would it be better if I did additions in this order:

1. implement the version_ tag handling
2. adapt the test db generation command to add versions
3. finish the overview tests

Or am I misunderstanding something?

[HuntTheSun]

Hi,

since I had some time I got started on the version_ tag handling in #158 , I hope I didn't have some errors in my thinking about the order.

[timdegroot1996]

so if I understand correctly, would it be better if I did additions in this order:
implement the version_ tag handling
adapt the test db generation command to add versions
finish the overview tests
Or am I misunderstanding something

There were 2 options.

1. Add a multiline command with --projectversion and create the tests with that. Then later improve it when version_ was implemented
2. What you described.

I quite like order 2 so great to see you already started the version_ implementation!

[timdegroot1996]

For your information, I released 1.4.0 so don't forget to pull all the latest changes!

Additionally I did 2 releases with the develop branch and it was just ugly as hell with commit messages and how it works so I'm ditching that way of working again. Sorry for the confusion. From now on you can simply merge into main and then I release when it's ready. If the docs update in the meantime I'll have to think about which PR's to merge when a bit better.

Good luck with this branch!

[HuntTheSun]

Hi, quick heads up, I can't finish this this weekend, sry. I got a decently high fever, I'm fit enough to clack keys on keyboard ofc but I probably wont get it to work properly, my brain wont brain properly.

[timdegroot1996]

Hi, quick heads up, I can't finish this this weekend, sry. I got a decently high fever, I'm fit enough to clack keys on keyboard ofc but I probably wont get it to work properly, my brain wont brain properly.

Oh that sucks man. Get well soon! The tests can wait 😄, health comes first