Project Synopsis
The project aims to update the client’s mobile app to provide a more seamless experience for its users.
The update includes several new features, such as the ability to track your package in real-time, access to order history and delivery updates, and the ability to add multiple addresses. The update also includes a redesigned interface that makes it easier for the users to navigate the app.
Collaborating with ValueCoders, the client expected a convenient way for customers to stay updated with their deliveries and receive assistance. An app through which customers can track their orders, view delivery progress, and receive real-time notifications. The app allows customers to rate their experience and sharing their valuable feedback. The goal is to let customers have the best possible experience with the app.
Project Requirement
This application will offer several advanced features, including improved security and easy tracking of packages and deliveries. It will allow users to rate and review the service along with real-time tracking.
As per the project’s requirement, clients and sellers will have the following 5 life-cycle states:
1. Onboarding
2. Active
3. Paused
4. Deboarding
5. Inactive
Type Of Users
1. Enduser
2. Admin
Project Flow
Client FPA is the shipper that provides orders, along with the information and fulfillment instructions, that are in turn acted upon by downstream operations resources. A client may operate via multiple entities (e.g. sellers, warehouse managers). Still, they maintain overall ownership of the order and are billed for services provided by the LSP post-order completion.
Key challenges
Problem Statement |
How We Resolved |
Manually testing of the entire project and process might miss some of the end-point to test before the deployment process or to handover the update to the client. |
We have implemented test cases of every function. It will automatically test all functions using dummy data provided in the same file. |
No tracking process of success and failure after manual testing of every function or APIs. |
After automation testing implement we can store success rate (in percentage) in a single file, can use in future if needed. |
Any check is not there that can stop the process of pipeline if the testing is not done perfectly. |
If anything is missing or something bad happen it will stop right away. |
Solution Implementation
Process
1. Testing clients’ login screen
2. Create dummy data to test clients and implement test cases
3. Create dummy API and usual testing as in postman or any software
4. Using the test command, get the percentage of implemented test cases of code
5. Deploy all test cases with files based on some test rules in Golang
6. Implement on codacy and get the percentage of deployed code
Documentation
Client FPA QA is best to implement before deploying it in the final environment. It will be useful to get code quality based on the percentage of test cases. We have to implement code and files based on some rules of technology. In Golang, we have to follow some rules, i.e., keep the original code and test file in a similar folder and some notation in the test file name.
Architecture
The architecture design document describes the components and specifications required to support the solution and satisfy the design’s specific business and technical requirements. QA is needed to implement and manage automation testing. Create API with some rules of technology.
Here we can implement with particulate notation follow; using a single command, we can execute all test files and get activities that cover code. Also, specific commands are there to execute specific API. Command will create another file for future purposes.
Results
The app has turned out to be a secure and trustworthy platform that allows the users to:
- Track their shipments in real-time, so they can always stay up-to-date on their location
- View order history and past invoices right from within the app
- Easily store all of your recipient addresses in one place with a built-in address book
- Manage all their deliverers from a single location