Let’s say we ran these commands and the .js file is created from a really huge api. That means it ended being a really huge file.
In addition to this context, we are also refactoring our API which means we will be converting our api with some high frequency.
From my understanding, every time we convert we can either overwrite our existing file and losing all our custom k6 lines in the process. Or, create a new file and lose our custom k6 lines added as well.
So we are thinking on some of organization that could allow us to convert our api with frequency but without losing our custom k6 added lines as much as we can.
This thinking led me to think about tags, and I found k6 tags and groups documentation -----> https://k6.io/docs/using-k6/tags-and-groups
We would still need to add tags to each request manually but cost / benefit, it seems to be minimal effort if we compare it with re-write everything again.
Does anyone has a project sample with these tests (tags & groups) we can take a look at?
Any other suggestion on the table?
Thank you very much,