search

cta-wave / dpctf-tests

Repo for DPCTF Tests. We prefer to keep the Tests separated from Test Runner
Other
1 stars 5 forks source link

long-duration-playback tests #121

Closed yanj-github closed 8 months ago

yanj-github commented 9 months ago

Current long-duration-playback tests doesn’t link with long duration content yet. However, from OF point of view, when we testing actual long duration content, we suggest user to run long-duration-playback tests on its own without having it together in same recording with other tests. This is because it took quite long to process longer duration test on OF. Also makes it easier to manage the storage and debugging. I suggest separating out long duration test on its own instead of having it inside same folder with other tests. Any objection please? Feel free to comment if you think otherwise.

jpiesing commented 9 months ago

I agree. How does this impact the project? Is this just a documentation issue or is there a technical change somewhere?

yanj-github commented 9 months ago

To run all test other than long duration, user requires to select a test group they want, e.g: cfhd_12.5_25_50-local then find long duration test and de-select it: image To run a long duration test find expected long duration test and select it and run.

I think it would be better to have long duration test in separate folder on test generation, so user does not have to exclude it.

jpiesing commented 9 months ago

@FritzHeiden In the screendump from @yanj-github above, long duration playback is in the same set as all the other AVC tests. Is it practical to either;

louaybassbouss commented 9 months ago

@jpiesing move it into a different set on its own is simple. I discussed this option yesterday with @FritzHeiden . The second option requires more time and changes in the UI. I propose to go with the first option and move to its own dataset?

jpiesing commented 9 months ago

@jpiesing move it into a different set on its own is simple. I discussed this option yesterday with @FritzHeiden . The second option requires more time and changes in the UI. I propose to go with the first option and move to its own dataset?

Whatever is the easiest way to avoid people running long duration playback by accident.

FritzHeiden commented 9 months ago

I moved the long duration tests into separate groups

yanj-github commented 9 months ago

It looks good to me. If no further comments this can be closed.

jpiesing commented 8 months ago

It looks good to me. If no further comments this can be closed.