add information about testing in workspace and components

[doudou]

No description provided.

[doudou]

@henriquejsfj could you have a read ? I'm very aware that it's probably hard to understand how to understand all of this ... I'd be very glad for a thorough review.

[henriquejsfj]

Very good! I never used workspace tests with cmake tests and all but the explanation seems to be enough.

[doudou]

Nice. You probably will have more comments once you've actually written the tests of the websocket controldev task, let's wait until then before merging this.

[g-arjones]

Pretty comprehensive... I missed one common case though: testing that ONE output port sends TWO samples in a row. I remember I needed this once and I couldn't manage, ended up creating a socket in my tests and connecting the iodriver's base subject to it by setting task.properties.io_port

I mean something like:

expect_execution { task.set_and_check_something }
    .to do
        [have_one_new_sample(task.io_raw_out_port),
         have_one_new_sample(task.io_raw_out_port)]
    end

[doudou]

In hindsight, a rather obvious need, actually.

Would need to refactor the have_one_new_sample add a more generic have_new_samples expectation with a count and then use it to "reimplement" have_one_new_sample.

Added an issue on syskit rock-core/tools-syskit#232

[g-arjones]

Thanks... 👍