The LinkedIn Consumer Solutions Platform enables sites and applications the power to enhance their sign-in experience using the world’s largest professional network. So it should support the use-case of sharing a post. The purpose of the UGC Post API is to support sharing. There is no need to create learning tests for the whole API, just the parts needed to support the use-case. The areas I’m looking into is the UGC Post API and Authorization. It contains at least 25 areas with many endpoints in each area. Continuously creating more tests and verifying that the existing tests don’t break. Then I extract code from the tests into my production code. I will only start writing the production code after I have a complete understanding of the API parts needed to support the use-case. But it might as well have been through a client library. In the LinkedIn example, I make HTTP calls directly. They can be applied to any third-party dependency. Learning tests are not restricted to testing REST APIs. It conflicts a bit with the TDD teaching where we write the test and then write the production code to make it pass. All the code is located in my learning tests. Notice that I don’t write any production code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |