openlmis-functional-tests

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Stopping execute functional tests on master node

It's true.. When I was testing it on uat I used this function from view requisitions and it failed on test server because there is this additional column for checkbox. I will think on another solut...

It's true.. When I was testing it on uat I used this function from view requisitions and it failed on test server because there is this additional column for checkbox. I will think on another solution here.

I think that we decided that it should be done in a separate ticket, but since we are already adding tests for navigating to the screen using navigation bar as a part of other screen related tests ...

I think that we decided that it should be done in a separate ticket, but since we are already adding tests for navigating to the screen using navigation bar as a part of other screen related tests we don't need it. Resolving.

change this step to when

change this step to when

Move this to the previous scenario

Move this to the previous scenario

These feel fragile and will fail if we change anything about the column order.

These feel fragile and will fail if we change anything about the column order.

I'm not sure whether this should be changed... Perhaps we should change the And I proceed to requisition for "Kankao Health Facility" facility, "Family Planning" program and "2017Q4" period step in...

I'm not sure whether this should be changed... Perhaps we should change the And I proceed to requisition for "Kankao Health Facility" facility, "Family Planning" program and "2017Q4" period step instead?

It would be better to have this at the end of previous scenario

It would be better to have this at the end of previous scenario

change to when

change to when

I separated it to another scenario

I separated it to another scenario

OLMIS-4575 improved approve-requisition feature steps

OLMIS-4575 fixed view requisition for approve requisitions screen

I don't understand why we submit and authorize a requisition if we only want to check if user without permission see an option in the navigation bar?

I don't understand why we submit and authorize a requisition if we only want to check if user without permission see an option in the navigation bar?

change to when

change to when

change to when

change to when

I don't see the When statement

I don't see the When statement

OLMIS-4575 added functional test for approving and rejecting a regular requisition
OLMIS-4575 added functional test for approving and rejecting a regular requisition
OLMIS-4575 fixed comparing total requisition cost value

OLMIS-5755: added check that SP name is required

OLMIS-5520: fixed setting up requisition form for submit

OLMIS-5755: added supply partner edit scenario (WIP)

    • -0
    • +15
    /src/pages/administration/supply.partner.edit.page.js
    • -0
    • +12
    /src/support/check/checkInputEnable.js
OLMIS-5520: moved submitting requisition to given steps

OLMIS-5520: moved datepicker methods to support package

    • -0
    • +4
    /src/support/action/datepickerSelectTodayDate.js
    • -0
    • +6
    /src/support/action/datepickerSetDateInFuture.js
    • -0
    • +3
    /src/support/check/checkCheckboxValue.js
    • -1
    • +3
    /src/support/check/verifyCheckboxValue.js
Maybe we could put these steps into another 'given' step, like "Given I have submitted a requisition for "Family Planning" program"? It's used this way in delete requisition feature.

Maybe we could put these steps into another 'given' step, like "Given I have submitted a requisition for "Family Planning" program"? It's used this way in delete requisition feature.

We have this thing in support, I will change it

We have this thing in support, I will change it