Quest 3 - Foolproofing Your API Client Library

NOTE: Getting rewards from this quest is over as it was only applicable on the Earn app when it was part of a campaign. Therefore, submissions are not reviewed or are disabled. However, you are highly encouraged to still complete the quest to practice your understanding.

When building an API Client Library, it's crucial to ensure it's foolproof. This means making it robust, easy to use, and error-resistant, ensuring that developers, even those less experienced, can use it effectively without encountering pitfalls.

One of the effective ways to make sure our API library is working correctly is including tests for our API library code!

We also experienced that not all data that we receive from the API is consistent with its types. Thus, this makes our early API library functions to work incorrectly.

To ensure that we are doing this the right way, we will follow basic steps from learning why software testing is important, and how to interpret error messages.

We will also let you experience what it’s like when you actually miss some parts of third-party documentation which is exactly what we need you to do for this module’s challenge! 👀

⚠️ Also, be aware that there is a challenge added to this quest. The challenge is part of the quest requirements. Be sure to follow carefully! (Now that this quest is converted to a tutorial, take your time to solve and finish the challenge requirements).

🔔 For more information, you may refer to this Zendesk article.

For technical help on the StackUp platform & quest-related questions, join our Discord, head to the 🆘 | quest-help-forum channel and look for the correct thread to ask your question.