I built a simple Odd One Out game where users have to find the item that doesn’t belong. The hardest part was handling the selection logic correctly, but I fixed it through debugging. happy that the app is now working and deployed online.
Deployed my Odd One Out project on Vercel. Fixed minor issues during deployment
Log in to leave a comment
I built the basic UI and added logic to check if the selected option is correct. i faced some issues with the selection logic but fixed them after debugging. I also made small UI improvements to make it cleaner.
Log in to leave a comment
I built a small physics project to show how objects fall in air vs vaccum. The main idea was to show that gravity is same, but air resistance makes a big difference. The hardest part was making the animation feel correct and fixing deployment issues (my file name was wrong at first), but I figured it out. I’m happy with how it turned out and learned both physics concept and some real deployment stuff.
During deployment, the updated UI was not showing because the main file was named “airVvacuum.html” instead of “index.html”. After renaming it and redeploying, the issue was fixed.
Log in to leave a comment
I created a simulation to show how objects fall in air and in vaccum. First, I designed the basic layout using HTML and CSS, then used JavaScript to add the falling animation. I applied the concept of gravity in both cases, and added air resistance only in the air part, so it falls slower compared to vaccum.
Log in to leave a comment
I built a full-stack game store web app using Spring Boot for the backend and plain JavaScript for the frontend. Users can browse games, add them to a cart, and place orders, and there’s also an admin side to manage games.
The hardest part was deployment. I faced multiple issues like wrong environment selection on Render, Dockerfile errors, path confusion, and Vercel deploying from the wrong folder. It took some time to debug things like build failures, API connection issues, and making the frontend and backend work together properly.
In the end, I was able to deploy the backend on Render and the frontend on Vercel, and connect everything successfully. I’m really happy that the project is now fully working live and I learned a lot about real world deployment and debugging
Worked on deploying my full-stack GameVault project. The backend is built using Spring Boot with PostgreSQL (Neon DB) and I deployed it on Render using Docker. Initially, I faced multiple issues like wrong runtime selection (Node instead of Java), Maven not found errors, and Dockerfile path problems. I also had to fix the Dockerfile naming issue (case sensitive) and understand how Render handles root directories and build context, for the frontend, I used plain HTML, CSS, and JavaScript and deployed it on Vercel. I ran into issues where Vercel was picking the wrong branch and root directory, so it wasn’t showing my frontend files. After correcting the root directory to the frontend folder and updating the API base URL to the deployed backend, everything started working properly. Finally i connected both frontend and backend, tested API endpoints, and verified that features like viewing games, cart, and admin operations are working correctly on the live deployment
Log in to leave a comment
Almost completed the backend part, still there are few bugs which I need to fix. Started working on the UI side, currently building login and register pages. Trying to connect frontend with backend APIs and testing the flow step by step.
Log in to leave a comment
Started working on the Game Store project. Set up the backend using Spring Boot and connected it with the database. Implemented basic authentication and role-based access control. Also created APIs for adding and managing games. Faced some issues with database configuration but fixed it after some debugging.
Log in to leave a comment
Added demo recording video link at Readme file and fixed the existing bugs
Log in to leave a comment
I built a Playwright automation framework to test a sample web application. It covers scenarios like login functionality, exception handling and table validations. The hardest part was understanding how fixtures and Playwright setup works, but I figured it out by trying different approaches and using trace viewer for debugging. I also learned how to generate HTML reports and deploy them using Vercel, which was really interesting. Overall, I got a better understanding of how real automation frameworks are structured.
bug fixed and deployed in vercel
Log in to leave a comment
Implemented fixture class and started understanding how Playwright fixtures works. Also explored codegen and trace viewer, it was really helpful to see step by step execution. Trace viewer is very useful for debugging issues and understanding what exactly happening during test run.
Log in to leave a comment
Started this project to practice Playwright automation and understand how UI testing works. First I created basic login test cases and tried interacting with elements on the Practice Test Automation site. Later I added few more scenarios like exception handling and table validations. Also learned how to generate HTML reports and push the project to GitHub using git.
Log in to leave a comment
I’m working on my first project! This is so exciting.
Log in to leave a comment
