That allows us to fetch data of all public boards of an user (on the API referenced as a “member”). Let’s first see if we can fetch some public data. Starting: Fetching the list of boards Sending a GET request If we can complete the API tests with pure frontend tests (network isolated) and contract tests, we can have the same level of confidence of the end-to-end test, but faster. An end-to-end (frontend + network + backend) test requires more processing than an API test (network + backend). You would need to pass through the water, the underwater sand and come back. Every failure would require debugging in a wider code area.Ģ - Performance: Imagine that you want to remove petrol from under the ocean. ![]() If we want to verify backend behavior through some of these interfaces, we will be fragile to errors in the interfaces: If a button is not rendered due a frontend bug, our test will fail, although the backend may be working as expected. However, there are two main reasons why these steps should be verified mainly on the API level:ġ - Precision: As mentioned, Trello has many frontend interfaces: mobile applications, desktop (which may vary in behavior in different browsers), etc. It’s true that we can do it using Trello’s frontend interfaces, either desktop or mobile - and Selenium scripts could drive our tests and verify the behavior.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |