Stops displaying page without imported id

[dimonioi4]

When running a test(test suite) through the CLI without the ID
example

type: Test
spec:
 name: POST_getCollectionOfUsers
 description: Import a description
 trigger:
   type: http

UI error:
Something went wrong!
TypeError: Cannot read properties of undefined (reading 'id')

No possibility to fail in test suite(testran)

To Reproduce
Steps to reproduce the behavior:

1. Run test suite with CLI without the ID
2. go to page Test suites
3. click run information
4. See error

Expected behavior
opens a page with information on running tests

Screenshots

Browser (please complete the following information):
Chrome.
v 122.0.6261.129, (x86_64)
Tracetest v0.15.3(open source version)

[danielbdias]

hi @dimonioi4 ! thanks for your report, we will take a look at it and return it to you as soon as we evaluate it.

[jorgeepc]

Hi @dimonioi4 thank you for reporting this issue. I tried to reproduce the bug using our latest version and v0.15.3 but I'm not seeing this problem. I'm using tests and testsuites definition files without IDs and everything looks correct on my side.

Are you seeing this problem consistently? And if that is the case, could you share the exact commands and definition files that you are using?

[dimonioi4]

Hi @jorgeepc interesting situation - this error seems to occur when trying to load UI list of tests in suite, and this problem is observed both in new some rans and old ones. And when trying to get them via API - everything is ok. At the moment it was not possible to localize and understand what data breaks the frontend

Thus, this error appears when trying to fail in UI in run after a short pause (there are tests in this test suite and run, but they failed to load and the startup error occurred earlier).

[dimonioi4]

In the console I also get these errors

[jorgeepc]

@dimonioi4 I think you are seeing the problem with new/old runs because you have a corrupted test without ID. Could you delete the test that is causing problems and see if you can reproduce the issue again? Or start with a fresh Tracetest instance and see if you can reproduce it?

[dimonioi4]

@jorgeepc Yes, I'll try to tidy up the tests (put id's on them). But it will take time, I'll come back with feedback later

[dimonioi4]

@jorgeepc Are there any restrictions on the display of ui - test id, test suite, variables - interested in this format id: yoTrZj1IR or no difference? This is important because I am generating test suites for CI and then I need to generate their id as well

[jorgeepc]

@dimonioi4 There are no restrictions. Remember that we support resources (test, test suites..) without IDs in your definition files. Then the first time you run them the CLI will add the ID automatically. However, as you are using them as part of your CI I would recommend having an ID for them.

[dimonioi4]

@jorgeepc I was able to fix the situation by recreating all the id's in the suite and in the tests and put them in a new suite
But the interesting thing is that all the tests from the broken set work and exist separately, nothing has changed in them. But the old suites and runs are not opening - magic