Skip to content

A test suite for 3PLs to run and test their Deliverr integration

Notifications You must be signed in to change notification settings

deliverr/warehouse-deliverr-tests

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

warehouse-deliverr-tests

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 service
  • USERNAME Deliverr's basic authentication username
  • PASSWORD Deliverr's basic authentication password
  • WAREHOUSE_ID A ID for one of your warehouse facilities
  • TEST_RUN the ith run of the tests

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
  • Get Product Details
  • Create Product
  • Update Product
  • Get Asn Status
  • Create ASN
After 1
  • Receive Asn Partially
  • Receive Asn Completely
  • Generate Inventory Movements (damaged, return, receive)
2
  • Get ASN Status
  • Get Inventory Movements
  • Get Inventory Status
  • Create Shipments
After 2
  • Fulfill orders (shipment)
  • Cancel a shipment
3
  • Get Inventory Status
  • Get Shipment Status
    After 3
    • Mark damaged units
      4
      • Get Inventory Movements

        How to run tests

        1. Clone the repository: git clone [email protected]:deliverr/warehouse-deliverr-tests.git
        2. Fill in .env. TEST_RUN is a number that has not yet been used before, starting at 0. 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.
        3. Run Tests Part 1: npm run test1
        4. 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.
        5. Run Test Part 2: npm run test2
        6. Cancel the order that has a note of "cancel this order". Fulfill all other orders with fake tracking numbers.
        7. Run Test Part 3: npm run test3
        8. Mark 2 units as damaged, with inventory movement type of ADJUSTMENT

        About

        A test suite for 3PLs to run and test their Deliverr integration

        Resources

        Stars

        Watchers

        Forks

        Releases

        No releases published

        Packages

        No packages published

        Languages