Maximo 7.6 version
MTSTUSER is loged in, using Condition codes application adds condition code.
This test proves that condition code can be added.
At the end condition code is deleted.
MTSTUSER is loged in, creates new inventory usage and enters data about it.
This test proves that data on the inventory usage page are same as on the list view.
At the end inventory usage is deleted.
MTSTUSER is loged in, creates new inventory usage and saves it
This test proves that new inventory usage can be created properly.
At the end inventory usage is deleted.
MTSTUSER is loged in, creates new inventory usage and checks it required fields.
This test proves that required fields are present at inventory usage.
At the end inventory usage is deleted.
MTSTUSER is loged in, creates new inventory usage and cancels it.
He uses Inventory Usage application.
This test proves that inventory usage can be canceled properly.
MTSTUSER is loged in, creates new inventory usage and change it's status to completed.
He uses inventory usage application.
This test proves that status of inventory usage can be changed to completed.
MTSTUSER is loged in, creates usage lines and check are required fields present.
He uses Inventory Usage application.
This test proves that there are all required fields present on inventory usage lines.
MTSTUSER is loged in, creates new non rotating item and adds it to storeroom.
He uses Item Master application.
This test proves that nonrotating item can be added to storeroom.