Get latest info on Bank jobs in India and preparing for IBPS common bank exams in 2017-2018.Also know how to prepare for IBPS bank exams, SSC exams and other govt. 2014年2月 代理店一覧に、有限会社白馬ヤマトヤが追加されました。 詳しくはこちら 2013年12月 西尾家具工芸社ショールーム. ![]()
What is Boundary value analysis and Equivalence partitioning? Software Testing Help. Boundary value analysis and Equivalence partitioning, explained with simple example: Boundary value analysis and equivalence partitioning both are test case design strategies in black box testing. Equivalence Partitioning: In this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce the total number of test cases to a finite set of testable test cases, still covering maximum requirements. In short it is the process of taking all possible test cases and placing them into classes. One test value is picked from each class while testing. E. g.: If you are testing for an input box accepting numbers from 1 to 1. Using equivalence partitioning method above test cases can be divided into three sets of input data called as classes. Each test case is a representative of respective class. So in above example we can divide our test cases into three equivalence classes of some valid and invalid inputs. Test cases for input box accepting numbers between 1 and 1. Equivalence Partitioning: 1) One input data class with all valid inputs. Pick a single value from range 1 to 1. If you select other values between 1 and 1. So one test case for valid input data should be sufficient. Input data class with all values below lower limit. I. e. any value below 1, as a invalid input data test case. Input data with any value greater than 1. So using equivalence partitioning you have categorized all possible test cases into three classes. Test cases with other values from any class should give you the same result. We have selected one representative from every input class to design our test cases. Test case values are selected in such a way that largest number of attributes of equivalence class can be exercised. Equivalence partitioning uses fewest test cases to cover maximum requirements. Boundary value analysis: It’s widely recognized that input values at the extreme ends of input domain cause more errors in system. More application errors occur at the boundaries of input domain. Boundary value analysis’ testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain. Boundary value analysis is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes. Test cases for input box accepting numbers between 1 and 1. Boundary value analysis: 1) Test cases with test data exactly as the input boundaries of input domain i. Test data with values just below the extreme edges of input domains i. Test data with values just above the extreme edges of input domain i. Boundary value analysis is often called as a part of stress and negative testing. Note: There is no hard- and- fast rule to test only one value from each equivalence class you created for input domains. You can select multiple valid and invalid values from each equivalence class according to your needs and previous judgments. E. g. if you divided 1 to 1. Same case for other test cases having invalid data classes. This should be a very basic and simple example to understand the Boundary value analysis and Equivalence partitioning concept. Share your examples below. SAP Explore - Blogs. This report will take delivery document number and delivery date from user and fetches details from delivery table and fetchescorresponding sales order details and billing details and displays sales order details with ALV list. Report sales_order_report .*"Table declarations............................... TABLES: likp. " SD Document: Delivery Header Data*"Selection Screen Elements........................... SELECT- OPTIONS: s_deldoc FOR likp- vbeln, " Deliverys_dldate FOR likp- lfdat. Delivery Date*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -** Type declaration of the structure to hold specified delivery header data **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *TYPES : BEGIN OF type_s_likp,vbeln TYPE likp- vbeln, " Deliverylfdat TYPE likp- lfdat, " Delivery Datekunnr TYPE likp- kunnr, " Ship- to party. END OF type_s_likp.*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ** Type declaration of the structure to hold specified delivery item data **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *TYPES : BEGIN OF type_s_lips,vbeln TYPE lips- vbeln, " Deliveryposnr TYPE lips- posnr, " Delivery Itemvgbel TYPE lips- vgbel, " Document number of the reference documentvgpos TYPE lips- vgpos, " Item number of the reference itemlfimg TYPE lips- lfimg, " Actual quantity delivered (insales units)vrkme TYPE lips- vrkme, " Sales unit. END OF type_s_lips.*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -** Type declaration of the structure to hold specified data in Customer Master **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *TYPES : BEGIN OF type_s_kna. TYPE kna. 1- kunnr, " Customer Number 1name. TYPE kna. 1- name. Name 1. END OF type_s_kna. Type declarations.....................................*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -** Type declaration of the structure to hold specified sales document header data **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -*TYPES : BEGIN OF type_s_vbak,vbeln TYPE vbak- vbeln, " Sales Documenterdat TYPE vbak- erdat, " Date on Which Record Was Createdaufnr TYPE vbak- aufnr, " Order Number. END OF type_s_vbak.*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -** Type declaration of the structure to hold specified sales document item data **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *TYPES : BEGIN OF type_s_vbap,vbeln TYPE vbak- vbeln, " Sales Documentposnr TYPE vbap- posnr, " Sales Document Itemmatnr TYPE vbap- matnr, " Material Numberarktx TYPE vbap- arktx, " Short text for sales orderitemkwmeng TYPE vbap- kwmeng, " Cumulative Order Quantity in sales Unitsvrkme TYPE vbap- vrkme, " Sales unit. END OF type_s_vbap.*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -** Type declaration of the structure to hold specified billing item data **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -*TYPES : BEGIN OF type_s_vbrp,vbeln TYPE vbrp- vbeln, " Billing Documentposnr TYPE vbrp- posnr, " Billing itemvgbel TYPE vbrp- vgbel, " Document number of the reference documentvgpos TYPE vbrp- vgpos, " Item number of the reference itemfklmg TYPE vbrp- fklmg, " Billing quantity in stockkeeping unitvrkme TYPE vbrp- vrkme, " Sales unit. END OF type_s_vbrp.*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ** Type declaration of the structure to hold specified sales socument * * header,sales document item data,delivery item data,billing item data **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *TYPES: BEGIN OF type_s_order,vbeln TYPE vbap- vbeln, " Sales Documentposnr TYPE vbap- posnr, " Sales Document Itemerdat TYPE vbak- erdat, " Date on Which Record Was Createdkunnr TYPE likp- kunnr, " Sold- to partyname. TYPE kna. 1- name. Name 1aufnr TYPE vbak- aufnr, " Order Numbermatnr TYPE vbap- matnr, " Material Numberarktx TYPE vbap- arktx, " Short text for sales orderitemkwmeng TYPE vbap- kwmeng, " Cumulative Order Quantity in sales Unitsvrkme TYPE vbap- vrkme, " Sales unitvbeln. TYPE lips- vbeln, " Deliveryposnr. TYPE lips- posnr, " Delivery Itemlfimg TYPE lips- lfimg, " Actual quantity delivered in sales unitsvrkme. TYPE lips- vrkme, " Sales unitvbeln. TYPE vbrp- vbeln, " Billing Documentposnr. TYPE vbrp- posnr, " Billing itemfklmg TYPE vbrp- fklmg, " Billing quantity in stockkeeping unitvrkme. TYPE vbrp- vrkme, " Sales unit. END OF type_s_order.*" Data declarations...................................*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ** Work variables **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *DATA : w_container TYPE REF TO cl_gui_custom_container," Reference variable for "containerw_grid TYPE REF TO cl_gui_alv_grid. Reference variable for grid*" Field String declarations...............................*"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -** Field string variable to hold sales socument header,sales document ** item data,delivery item data,billing item data,fieldcatalog,layout record **"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - - -- -- -- -- -- -- -- -- -- -*DATA : fs_kna. TYPE type_s_kna. 1, " Holds Customer master recordfs_vbak TYPE type_s_vbak, " Holds sales header recordfs_vbap TYPE type_s_vbap, " Holds sales item recordfs_likp TYPE type_s_likp, " Holds delivery header recordfs_lips TYPE type_s_lips, " Holds delivery item recordfs_vbrp TYPE type_s_vbrp, " Holds billing item recordfs_order TYPE type_s_order, " Holds sales order recordfs_cat TYPE lvc_s_fcat, " Holds fieldcatalog recordfs_lay TYPE lvc_s_layo. Holds layout record*" Internal Table declarations..............................**"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *** Internal Table to hold hold sales socument header,sales document ** item data,delivery item data,billing item data,fieldcatalog,layout records ***"- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- *DATA : t_kna. LIKESTANDARD TABLEOF fs_kna. Internal table to hold customer master recordst_vbak LIKESTANDARD TABLEOF fs_vbak, " Internal table to hold sales header recordst_vbap LIKESTANDARD TABLEOF fs_vbap, " Internal table to hold sales item recordst_likp LIKESTANDARD TABLEOF fs_likp, " Internal table to hold delivery header recordst_lips LIKESTANDARD TABLEOF fs_lips, " Internal table to hold delivery item recordst_vbrp LIKESTANDARD TABLEOF fs_vbrp, " Internal table to hold billing item recordst_order LIKESTANDARD TABLEOF fs_order, " Internal table to hold sales order recordst_cat TYPE lvc_t_fcat.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2018
Categories |