Why not generate these Artifacts with API calls?

Using API calls for a task does mean quicker and more stable testing, as it directly communicates with an application. It can be implemented earlier in the development process. This could lead to early detection of issues, making the development process more flexible and agile.

Conversely, using an automated GUI could provide a richer understanding of the user experience, as it can simulate the exact paths a user might take, including interactions with visual elements that API tests might overlook. This approach might be more intuitive and can encompass a broader analysis, including the appearance and layout, which are crucial for user satisfaction.

In fact, there is no reason to support once approach over another. The GUI approach confirms the system works correctly for the user. The API approaches generate the artifacts with greater speed. We can implement the differences in the approaches by adding another keyword value to...