Mr. Lancer 987's Blog

In this post, I’ll be reflecting on my group’s first sprint towards developing an Identity Access Management System for Thea’s Pantry. Our focus in Sprint 1 was really to get a base understanding of Keycloak and to implement a basic framework that would allow us to integrate Keycloak with the pre-existing systems. Some of my personal work towards that goal was as follows: GitLab Documenting our low-level issues in GitLab and assigning them accordingly. Epic Backend Create API endpoint specification and schemas for role checking functionality. Endpoint , Schemas Create test calls with mock JWTs to test the endpoint. Test Call Implement backend JWT processing/decoding logic. CheckRole.js Implementation Frontend Containerize the fake frontend in a way that allows it to interact with the backend for testing purposes. Containerization Create a dummy frontend with buttons that send mock JWTs to the new backend endpoint for testing purposes. This frontend sends encoded JWTs that contain user...

  In this post, I’ll be discussing a recent article I came across on the TestRail website, which can be found here . The post interested me because it dives deep into the importance of organizing and managing test cases effectively, a topic that we have been covering closely in class. As someone who does a lot of tests in various stages, this article gave me some good notes about how proper test case management can streamline the testing process and reduce the risk of overlooked issues. One of the key takeaways from the article was the concept of structuring test cases with clear, concise steps and expected outcomes. This was notable because I’ve often seen situations where poorly written test cases lead to confusion or unnecessary delays. The article emphasized that each test case should be easily understandable, even for someone unfamiliar with the project, which makes a lot of sense. Clear test cases not only make the process smoother for current testers, but they also provide b...