PharmaStock Authentication and AI Testing

 This week I focused on completing the authentication workflow for PharmaStock and testing the new AI integration that was recently added to the project.

The main task I worked on was connecting the Angular login screen to the ASP.NET Core backend authentication endpoint. I implemented the login flow so that when a user enters their email and password, the frontend sends a request to the API login endpoint. When the credentials are valid, the backend returns a JWT token that is stored locally so it can be used for future authenticated requests.

After implementing the login functionality, I tested the system using both the seeded admin account and a newly created test user. I verified that the login request returned the correct token and that user roles were stored properly in the database.

I also spent time testing the AI prediction pipeline that was recently integrated into the project. Initially, some prediction endpoints were returning server errors, but I discovered the issue was related to the AI Docker container not running locally. After starting the container, the AI service responded correctly to health checks and confirmed that the machine learning models were loaded successfully.

Overall, this week’s work helped ensure that the authentication system is functioning correctly and that the AI service is accessible for future features within the application.




Comments

Post a Comment

Popular posts from this blog

PharmaStock: Backend Infrastructure & Database Connectivity

 This week marked the transition from planning and design into real backend development. After organizing the project structure and defining use cases in previous weeks, I focused on building the technical foundation that the rest of the application will depend on. The primary goal was completing SCRUM-16, which involved connecting the ASP.NET Core backend API to a MySQL database and verifying that the system could successfully generate and manage database tables. I began by configuring MySQL to run inside a Docker container. Using Docker ensures that every developer on the team works against the same database environment, which reduces setup inconsistencies and avoids the common “it works on my machine” problem. Once the container was running correctly, I verified that it could be started, stopped, and inspected reliably. Next, I integrated Entity Framework Core with the Pomelo MySQL provider and registered the DbContext within the application. This step allows the backend to m...
Read more

PharmaStock Backend Progress Complete all backend endpoints

Image
 I completed the full Medication API (GET, POST, PUT, PATCH, DELETE) and finished SCRUM-37, implementing the stock quantity adjustment endpoint. Inventory quantities can now be increased or decreased, negative values are prevented, and all changes persist correctly in the database. I also finalized the inventory creation flow with duplicate lot validation and verified everything through Swagger testing. On the frontend side, I started SCRUM-38 and began building the Angular inventory list component to connect the UI to the new backend functionality. Overall, this week solidified the backend foundation and began transitioning into full-stack development. Medication Post Workflow            Medication Post          Post Inventory for new medication               Inventory adjustments
Read more

PharmaStock: Sprint Planning Complete

This week was focused on finalizing project planning and getting everything ready for development. I completed the setup of the Jira board , finalized all sprints for the full length of the project, and added clear completion criteria for each sprint and task. This gives the team a clear roadmap from MVP through enhancement features. I also synced my local GitHub setup with the main project repository and verified that the branching structure is ready for feature development. With planning complete and source control aligned, the project is now fully prepared to move into active development next week.
Read more