A test suite for 3PLs to run and test their Deliverr integration
Assuming that the warehouse has implemented API as per the Postman documentation
This test suite will test the endpoints from the Postman documentation. The following needs to be defined in the .env file before running the test suite
SERVICE_URL
the endpoint for your backend serviceUSERNAME
Deliverr's basic authentication usernamePASSWORD
Deliverr's basic authentication passwordWAREHOUSE_ID
A ID for one of your warehouse facilitiesTEST_RUN
the ith run of the tests
A single test run is divided into 4 parts.
After each test part is run, you are expected to handle the entities that have been created in your warehouse system (receiving ASN, fulfilling an order, cancelling an order,...), prior to running the next test part:
Test Part | Details |
---|---|
1 |
|
After 1 |
|
2 |
|
After 2 |
|
3 |
|
After 3 |
|
4 |
|
- Clone the repository:
git clone [email protected]:deliverr/warehouse-deliverr-tests.git
- Fill in
.env
.TEST_RUN
is a number that has not yet been used before, starting at0
. For every new test run (after going through all test parts), increment this by 1 so that it can be tracked in the warehouse's system. - Run Tests Part 1:
npm run test1
- In your warehouse system, fully receive the ASN that has expected quantity of 5 units, and receive 5 units of the ASN that has expected quantity of 10. Do not receive the ASN that has quantity of 1 unit.
- Run Test Part 2:
npm run test2
- Cancel the order that has a note of
"cancel this order"
. Fulfill all other orders with fake tracking numbers. - Run Test Part 3:
npm run test3
- Mark 2 units as damaged, with inventory movement type of
ADJUSTMENT