-
I know there has been discussion of whole-suite recording and that that's hard, BUT, I just want tests to record something useful. Right now I have tests like this:
That will record 3 videos, which isn't what I want. But if I remove all the "its" then I will have less useful textual output. Is there a way to get recordings to work at the "describe" level instead of the "it" level? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
@djMax we have no such capabilities ATM, I'm afraid. Nevertheless, we've had discussions over it in the past and would like to support that at some point in the (far) future. As a suggestion, you might consider introducing recording by yourself (i.e. look up the associated commands in the Detox log, and utilize yourself in In any case, I'm intrigued -- why are the test-granularity videos useful? I'm inclined to say that it has something to do with the fact that you do not relaunch the app or |
Beta Was this translation helpful? Give feedback.
-
We do reload on each "suite" - so once per file basically. But right now, our "it" tests are like 1 screen entering data and clicking "next" and then the next "it" is the next screen or next action. So the recordings end up being totally useless because they don't capture the before/after transitions, which is usually where the problem hides. I get your point about doing our own recording - that probably is the easiest path. |
Beta Was this translation helpful? Give feedback.
@djMax we have no such capabilities ATM, I'm afraid. Nevertheless, we've had discussions over it in the past and would like to support that at some point in the (far) future.
As a suggestion, you might consider introducing recording by yourself (i.e. look up the associated commands in the Detox log, and utilize yourself in
beforeAll()
andafterAll()
).In any case, I'm intrigued -- why are the test-granularity videos useful? I'm inclined to say that it has something to do with the fact that you do not relaunch the app or
reloadReactNative()
before each test, which isn't good practice.