|
|
| Line 1: |
Line 1: |
| − | ===Libero Test Plan===
| + | For all ages, people are http://www.compraruggbootsloja.com/ already experimenting and making the most of styling their hair. A man or grownup females commonly requires attention of her or his hair, regardless of once the way in which is uncomplicated as running a http://www.christianlouboutinshoesboots.com/ comb or as complex as placing several chemicals, because of this of http://www.monclerpresa.com/moncler-men-s-vests.html truth that distinctive purpose while using staff system is often a person's crown of beauty. |
| | | | |
| − | '''Overview'''
| + | With the creation of electric hairstyling http://www.monclerpresa.com/moncler-negozio.html devices, hairstyling will become exceptionally easy, convenient, and fun. there can be now high temperature combs, frizzy hair curlers, and frizzy hair irons furthermore regarding the limitless http://www.monclerpresa.com/moncler-women-s-coats.html choice of environment and coloring chemicals. |
| − | | + | |
| − | Libero implements alot of complex functionality. I am a strong advocate of extreme programming type methedologies and writing lots of unit and functional tests is vital to confirming functionality. It is especially important to have good working unit and functional tests for complex functionality when changes are made to Libero to confirm that the changes did not break important functionality. That is the goal of this Libero Test Plan.
| + | |
| − | | + | |
| − | '''Testing Approach'''
| + | |
| − | | + | |
| − | One of the most important parts of doing unit/functional tests is the ability to know the state of the application your testing both before and after the test. To achieve this goal I am going to assume that a new client/company has been created from the initial datbase dump. As a result the AD_Client_ID would be 1000000 etc... and this would be known by the unit/functional tests. All new records should be removed after the suite of tests is run.
| + | |
| − | | + | |
| − | '''Highlevel Objects that need to be setup for Testing Libero'''
| + | |
| − | | + | |
| − | The minimum objects that need to be created to test all aspects of Libero are:
| + | |
| − | | + | |
| − | 1. Business Partner Customer
| + | |
| − | 2. Business Partner Supplier
| + | |
| − | 3. Create a Product that is purchased from the Business Partner Supplier created in step 2
| + | |
| − | 4. Create a Product that is manufactured
| + | |
| − | 4.5. Create a High Level manufactured Product
| + | |
| − | 5. Create a BOM associated with a high level product that depends on the manufactured product and the purchased product
| + | |
| − | 6. Create a manufacturing resource type
| + | |
| − | 7. Create a manufacturing resource of type plant
| + | |
| − | 8. Create a manufacturing resource of type production line
| + | |
| − | 9. Create a manufacturing resource of type workcenter
| + | |
| − | 10. Create a manufacturing resource of type workstation
| + | |
| − | 11. Create a manufacturing workflow that uses the defined manufacturing resource in steps 7 - 10 to create the product defined in step 4
| + | |
| − | 12. Create a product planning object that links the workflow created in step 11 and BOM created in step 5
| + | |
| − | 13. Verify the products created in steps 3 and 4
| + | |
| − | 14. Verify the BOM created in step 5
| + | |
| − | 15. Validate the manufacturing workflow created in step 11
| + | |
| − | 16. Create a sales order with a single order line of the product defined in step 5
| + | |
| − | | + | |
| − | '''Lowlevel Objects that need to be setup for Testing Libero'''
| + | |
| − | | + | |
| − | I will now provide a more detailed specification of the minimum objects that need to be created to test all aspects of Libero.
| + | |
| − | | + | |
| − | ===Lowlevel Object Definitions===
| + | |
| − | | + | |
| − | {| border="1"
| + | |
| − | !#||Name!!Description!!Attributes!!Java Object!!Notes
| + | |
| − | |-
| + | |
| − | |1||Test Business Partner Customer||A test business customer that can purchase the highlevel product||Name: Test Business Partner Customer<br>||MLocation, MBPLocation, MBPGroup, MBPartner ||None
| + | |
| − | |-
| + | |
| − | |2||Test Business Partner Supplier||A test business supplier that can supply the purchased product||Name: Test Business Partner Supplier<br>||MLocation, MBPLocation, MBPGroup, MBPartner ||None
| + | |
| − | |-
| + | |
| − | |3||Test Purchased Product||A test purchased product||Name: Test Purchased Product<br>||MProduct||None
| + | |
| − | |-
| + | |
| − | |4||Test Manufactured Product||A test manufactured product||Name: Test Manufactured Product<br>||MProduct||None
| + | |
| − | |-
| + | |
| − | |4.5||Test Manufactured High Level Product||A test manufactured High Level product||Name: Test Manufactured HL Product<br>||MProduct||None
| + | |
| − | |-
| + | |
| − | |5||Test Manufactured BOM||A test manufactured BOM||Name: Test Manufactured Product<br>||X_PP_Product_BOM, X_PP_Product_BOMLine||None
| + | |
| − | |-
| + | |
| − | |6||Test Manufacturing Resource Type||A test manufacturing resource type||Name: Test Manufacturing Resource Type ||X_S_ResourceType, org.eevolution.model.X_S_Resource||None
| + | |
| − | |-
| + | |
| − | |7||Test Manufacturing Resource Plant||A test manufacturing resource Plant||Name: Test Manufacturing Resource Plant ||org.eevolution.model.X_S_Resource||None
| + | |
| − | |-
| + | |
| − | |8||Test Manufacturing Resource Line||A test manufacturing resource line||Name: Test Manufacturing Resource line ||org.eevolution.model.X_S_Resource||None
| + | |
| − | |-
| + | |
| − | |9||Test Manufacturing Resource Workcenter||A test manufacturing resource workcenter||Name: Test Manufacturing Resource workcenter ||org.eevolution.model.X_S_Resource||None
| + | |
| − | |-
| + | |
| − | |10||Test Manufacturing Resource Workstation||A test manufacturing resource workstation||Name: Test Manufacturing Resource workstation ||org.eevolution.model.X_S_Resource||None
| + | |
| − | |-
| + | |
| − | |11||Test Manufacturing Worflow Route||A test manufacturing workflow route||Name: Test Manufacturing Workflow Route ||MWorkflow, MWFNode, MWFNodeNext, X_PP_WF_Node_Product||None
| + | |
| − | |-
| + | |
| − | |12||Test Manufactured HL Product Planning||A test product planning object||Name: Test Manufactured HL Product Planning ||MPPProductPlanning||None
| + | |
| − | |-
| + | |
| − | |16||Test Sales Order||A test sales order||Name: Test Sales Order ||MDiscountSchema, MDiscountSchemaLine, MPriceList, MPriceListVersion, MProductPrice, X_C_Order, X_C_OrderLine||None
| + | |
| − | |}
| + | |
| − | | + | |
| − | | + | |
| − | [[Category:LIBERO]]
| + | |
| − | | + | |
| − | ===Unit/Functional Tests===
| + | |
| − | | + | |
| − | | + | |
| − | {| border="1"
| + | |
| − | !#||Given!!Steps!!Notes!!Expected Result
| + | |
| − | |-
| + | |
| − | |1||All minimum objects setup for testing Libero Functionality||Run the CalculateLowLevel process||The calculate low level process calculates and registers the lowest level of a product inside any BOM. It is used in the MRP calculations and should be executed when you enter a new BOM||The lowlevels of the products defined are: TBD
| + | |
| − | |-
| + | |
| − | |2||All minimum objects setup for testing Libero Functionality||Run the CalculateLowLevel process. Then run the Create Record MRP Process||The create record mrp process deletes all records of MRP and generate them again. The create record mrp process also recreates the demand, approved, and open orders for a product||TBD
| + | |
| − | |-
| + | |
| − | |3||All minimum objects setup for testing Libero Functionality||Run the CalculateLowLevel process. Then run the Create Record MRP Process. Then run the regenerate material plan. Then run the capacity plan calculation process with forward scheduling||The capacity plan calculation process adjusts the manufacturing order scheduled start time and scheduled end time ||TBD
| + | |
| − | |}
| + | |
