Trisha Chetani - Assiduous test the APIs for better software delivery
What is your experience with designing and building APIs?
I have experience in designing and building the API test from a testing perspective. I have involved myself in the conversation where developers were designing and building APIs.
However, I have done a small POC from the perspective of self-learning how to build APIs https://github.com/TrishaChetani/SpringRestAPIApplication
While creating API Designs, implementing and / or consuming and testing them, what challenges have you faced / are facing?
I have faced the challenge that there is no clear requirement from the API perspective so that the tester could plan to test it better.
- Since the changes in APIs are not planned well, so there is formal communication across the team. It leads to rework in the team. For example, the front-end developer has to rewrite the code, and the tester has to rewrite the test.
- The whole team collaboration is missing. Since the business is not aware and the focus shifts to how many user-impacted features are delivered. This leads to the situation inside the team growing more technical debt day by day. (For example, significant bigger request payloads, long response time, too much data or irrelevant data in response, no versioning, no SSL, no clear error code or error message)
- Since there is no clear definition, it is easier for a developer to reject the bugs. This is also because most of the team is having a high-level strategy but not at each layer.
What lessons have you learned with regards to designing and testing APIs?
- I learnt the lesson that API and backend changes should be documented, communicated and planned well.
- Having API functioning better improves application usability, security, and performance which in turn brings more users and leads to bigger business.
- rapidly build clear and complete flows of API
What do you plan to learn /explore at this conference?
How different teams are approaching?
What are the challenges for the different teams and how they are overcoming them?
Network with people
How do you plan to contribute?
- Techniques for mapping of API specification to test specification.
- A strategy to tests so that most of the testing is covered in the lower layer and which in-turn makes your testing more targeted. For example, positive flow, and negative flow includes error codes, permissions, boundary values, and logical testing, contract-based testing.
- Techniques for reporting and monitoring
Call for Papers CLOSED
Ended on Oct 30 '22 11:59 PM IST
In our experience, having participants write a position paper before coming to the conference leads to better discussion because people have thought about what they want from the conference. Last thing we want is to spend half of the conference time figuring out what you want to figure out.
A Position Paper is a simple paragraph which answers the following questions:
- What's your experience with designing and building APIs?
- While creating API Designs, implementing and / or consuming and testing them, what challenges have you faced / are facing?
- What lessons have you learned with regards to designing and testing APIs?
- What do you plan to learn /explore at this conference?
- How do you plan to contribute?
* Note that the above questions are just pointers, you don't have to answer each one point by point.
