fitness语法总结.doc

加载setup!|Load Setup Data|RepairTypeSetup|Go! | |记录测试脚本历史!|Set Test Revision History |Rev Date |Name |Reason for Modification |Enter!|03/10/2010|Tom & Saif|Add for B-01332 |True |09/28/2011|Steph |Alternate Accounting Changes B-03719|True |打开一个form!|Open Search Form|Repair Type |Form Mode |EntityType |Enter! |new |RepairTypeSearch|RepairTypeSearch_form|检查字段有效性Make sure fields are enabled!|Check|that the field|Repair Group |is enabled|True |检查必输项字段The following required fields should be in error because they are currently blank.!|Check|that the field|Repair Group |is in error|true|Check |that the field|Repair Type |is in error|true|Check |that the field|Repair Type Description|is in error|true|ActionEg!|Perform Action|Create| 或 !|Perform action|New_|给字段设值|Set Form Fields |Branch |Go! |Car1 |True |检查radio button的默认值Repair Type Status should default to Active!|Inspect Form Fields |Print Parts Detail|Print Labor Detail|Status| |All |All | Active|检查隐藏字段!|Check|thatthefield|lblItemTypeDescription|isvisible|false| QuickList3:8088/FrontPage.ProfitMaster.ProfitMasterSetUp.QuickList清空数据库!|Karmak.ProfitMaster.Fitnesse.PMSession|!|Set Test Attributes|Test Number|Status|Enter!|SYS99999-900|Proven|!|sleep|2|!|Login User|!|Cleanup Test|-!1 Common Test Errors!2 Object reference not set to an instance of an objectthis just means that some area of the code is trying to do something that it is not fully set up for. There is some setup required that is missing. It is a very generic exception that can be caused by many different things. This can often be the result of other errors in the test. If there are no previous errors to resolve, then a developer will have to debug the test to reach the point that errors to determine the problem. Most of the time these exceptions include the section of code, to make it easier for the developer to find where to debug.!-System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. System.NullReferenceException: Object reference not set to an instance of an object. at Karmak.BusinessServices.PM.ACT.AccountsReceivable.Process.ProcCustomer.get_CustomerPO()-!2 window handlesif you ever see window handles in the text of an exception, this means your test has opened forms too many times, exceeding the resources of the machine. the only solution is to open fewer forms, either by using Enter Object instead for data creation, or using Select Form to reuse the same form repeatedly instead of reopening it each time it is needed.window handles errors can sometimes be preceeded by other more normal seeming errors. dont let this distract you, if there is a window handles error anywhere in your test, that must be resolved first.also note that since the these errors are resource related, you can get different results on different machines, current, future, local, etc.-!1 Set Test Attributesset test attributes is only necessary because the Enter column indicates if the test is running locally or on the fitness machine, and if it is running on the fitness machine, it indicates which database to select from the options dropdown on the login screen.!|Set Test Attributes|Test Number|Status|Enter!|SVO22200-022|Concept|-!1 Working with a treeview control on a formthe accounting setup form is an example of a form with a treeview on it. in these 3 lines, you select the treeview control, select a particular item/node, then perform an action on that item as you would in the application.!|Select control|Accounting Setup Tree|Select item|A/P Vendor|Perform Action|Expand|-!1 Working with a listview controllistview fixtures are very similar to grid fixtures.!|Inspect ListView Contents|lvwGLControl|Value |first |second |third |!|Select List View|lvwGLControl|Row|second|-!1 Required field defaults.when a new required field is added to a form, and we dont want to have to go back to existing tests to make them set that new field, we can cheat! for these forms, if any of these required fields is not set, the record will be saved with the following default setting. So even though in the app the Save button would not be enabled, we can still save these records in fitnesse.Branch:* !-NextReservationAgreementNumber-! = 1000* !-MaxReservationAgreementNumber-! = 999999* !-ResetReservationAgreementNumber-! = 1000* !-DailyTo-! = 5* !-WeeklyFrom-! = 6* !-WeeklyTo-! = 10* !-MonthlyFrom-! = 11* !-MonthlyTo-! = 30* !-YearlyFrom-! = 31* CustomerBaseBranchID = 1Customer:* CustomerBaseBranchID = 1* ControlBranchID = 1-!1 Making a comment big bold and pink.The following is what we used to use for pointing out that a test is different from Current.!-! This test has been changed for Future ONLY. This makes it different from Current. No more overlaying! !-!-!1 MessagesSetting messages!|Set message|SYS008|response to|Ok|Checking to see if a message came up!|Check|that the message|SYS008|was called|true|Command to prompt for a message that changes with different variables and shows them in the message.!|Check|That Message|SVO004|Has Key|%MissingAccounting%|With Value|Labor Inventory, Labor Cost, Labor Sales, Payment Method|(ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderHeaderMaintenanceTop.FunctionalArea.InvoiceRequest)-!1 Setup DataLoading!|Load Setup Data|CustomerRoInvoicesSetup4|Go!|Ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.AccountinG.CustomerRoInvoicesTop.FunctionalArea.VoidPaymentApplicationForm-Storing!|Store Setup Data|CustomerRoInvoicesSetup4|Go!|Ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.AccountinG.CustomerRoInvoicesTop.FunctionalArea.SharedInitialization4-!1 UsersLogging in as Demo!|Login user|Logging out a user!|Logout User|Logging in as a specific login different from Demo!|Login user|DanM|with password|DanM|into Branch|Car1|and Department|Service|-!1 PermissionsSetting a permission for a specific user group!|Set Permission|Allow to modify regardless of status|To Value|False|For Application|PSS21750|Where User Group Is|Branch Manager|Ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderPartsMaintenanceTop.FunctionalArea.AccessOtherModulesFromPartsPermission-!1 Branch Parameters / Branch Dept parametersSetting a parameter for a BranchThis fixture doesnt ask for a branch and simply will set the branch that the user is logged into when you set it thru FitNesse. So if youre logged into the Demo/Demo from Branch Car1. Car1 is what is getting set!|Set branch parameter|219|To|True|Setting a parameter for a branch/dept!|Set Branch|Car1|Department|Service|parameter number|71|Value To|1| Ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderHeaderMaintenanceTop.FunctionalArea.AutoInvoiceAlternateBillingRo-!1 TimeFreezing Time!|Set system time|03/15/2010 11:50 AM|-!1 Forms/AppsOpening a new form!|Open Search Form|RepairOrder|Form Mode|EntityType|Enter!|new|RepairOrderSearch|RepairOrderSearch_Form|Leaving a form and storing it as a variable to reselect later!|Check|Last FormID Is|RepairOrderEntry_Form|Re-selecting that form at a later time!|Select form|Repair_Order_Parts_Form|Closing a form!|Close form|Ex: the above 4 were on: http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderPartsMaintenanceTop.FunctionalArea.AccessOtherModulesFromPartsPermissionClicking FIND on a toolbar in a Search Form!|Perform action|Search|Inspecting standard fields on a search grid!|Inspect Search Results|Branch|Repair Order|Customer|Company Name|Unit|Car1|1000|50001|Bikini Bottom Trucks|Unit 202|Hitting NEW on a standard search form to launch maintenance form in new mode!|Perform action|New_|Inspecting Form fields on a standard maintenance form!|Inspect Form Fields|Pricing Matrix|Price|Markup|Inactive|$0.00|0.0|False|Validating if fields are enabled or disabled on maintenance form!|Check|that the field|Pricing Matrix|is enabled|true|Check|that the field|Price|is enabled|true|Check|that the field|Markup|is enabled|true|Check|that the field|Inactive|is enabled|true|Validate if fields are required or not!|Check|that the field|Pricing Matrix|is in error|true|Validate if fields are visible or not!|Check|that the field|Pricing Matrix|is visible|true|Ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.InventorY.InventoryDetail.FunctionalArea.CreateInventoryDetailTesting if toolbar action buttons are available or not - IF THEY ARE ONE WORD!|Check|that the action|Save|state is|false|Check|that the action|Cancel|state is|true|Testing if toolbar action buttons are available or not - if they are MORE THAN ONE WORD!|Check|That the Toolbar Button|Print Quote|state is|true|!|Check|That the Toolbar Button|Open Quote|state is|true|Setting fields on a standard maintenance form!|Set Form Fields|Pricing Matrix|Go!|Retail 4|True|Hitting SAVE on a maintenance form!|Perform action|Save|Selecting Cancel on a maintenance form!|Perform action|Cancel| Selecting VIEW on a maintenance form!|Perform action|View| Selecting EDIT on a maintenance form!|Perform action|Edit|Setting a message because an action causes the message to popup!|Set message|SYS001|response to|Ok|!|Perform action|Save|!|Check|that the message|SYS001|was called|true|-!1 Validating Title Bar and Side Panel in 3.0 search/maintenace forms also validating horzontal tabsThe following is how you inspect the title bar.!|Check Form Specs|Title|INV95000 Receive Inventory|Inspect side panel that should currently simply say New!|Inspect Open Form Parts|Short Title|Search|New|And then once you go into Edit or View, you would say something like this depending on the g/w/tIn my scenario, the POs wanted the Branch, a dash, then the Reference number!|Inspect Open Form Parts|Short Title|Search|Chicago - 1500|To validate a horzontal tab!|Check|that the tab|Retained Earnings|exists|true|-!1 Setup Pages Putting a setup page in a test!include ProfitMaster.ProfitMasterSetUp.QuickList-!1 VTL Clicking a VTL button (binoculars)!|Click Vtl Button|Payment Method|We must register the selection form as the currently active form!|Set Selection Form|Payment Method|The only payment methods available are supposed to be ones with a payment type!|Inspect Data Grid|DataGridBase1|Payment Method|Payment Type|Create A/R|Inactive|On Account|$CHARGE_ID|True|False|On 2Account|$CHARGE_ID|True|False|On 3Account|$CHARGE_ID|True|False|!|Select Grid Row|DataGridBase1|where|Payment Method|equals|On 2Account|!|Click button|Select|Ex: the above was found in http:/fitnesssvr:8088/FrontPage.ProfitMaster.AccountinG.FinanceCharge.FunctionalArea.NewFinanceCharge-!1 Part Number VTLThe following shows a scenario where I enter a part that isnt unique so the VTL selection form pops up. The user would have to select the part the want and return back to calling form. This example is in Receiving Inventory program!|Set Grid Fields|ReceivingInventoryGrid|PartNumber|Go!|515Gasket-2|true|It pops up the parts vtl selection form. I must choose the exchange part.!|Set Selection Form|Receive_Inventory|with column|Part Number|!|Inspect Data Grid|DataGridBase1|Supplier|Part Number|Description|Part Type|Quantity Available|ACT|515Gasket-2|Gasket|Exchange|-5|ACT|515Gasket-2|Gasket-Core|Core|0|!|Select Grid Row|DataGridBase1|where|Part Number|equals|515Gasket-2|and|Description|equals|Gasket|!|Click Button|Select|Note that this part is under the assumption youve defined the receive inventory form as this earlier in the test!|Select Form|Repair_Order_Parts_Form|!|Perform action|Edit|!|Select grid|Parts Detail|row|1|!|Double click|Parts Detail|Grid Cell at Column|1|and you can find an example of it here:http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderPartsMaintenanceTop.FunctionalArea.ChangePartByCreatingNewOne-!1 Selecting a row in editable data grid and setting field to something!|Select grid|ctlInvoicesGrid|row|1|!|Set Grid Fields|ctlInvoicesGrid|Pay|Go!|True|True|EX: http:/fitnesssvr:8088/FrontPage.ProfitMaster.AccountinG.CustomerRoInvoicesTop.FunctionalArea.SearchInvoiceVoidPaymentZeroValue-!1 Current Application in FocusTesting which application is in focus!|Check|That the active form part is|Parts|This will check what form/tab is in focus. like in a standard search / maintenance form which along the side panel are in focus. In this case its the panel labeled Parts.Ex: http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderPartsMaintenanceTop.FunctionalArea.CheckConcurrencyMessagesInMiscInfo-!1 Clicking to a different TAB in a form. (sometimes this is not necessary however)!|Click Tab|tpgAttachedDocuments|EX: http:/fitnesssvr:8088/FrontPage.ProfitMaster.ServiceOperation.RepairOrderHeaderMaintenanceTop.FunctionalArea.EditRoInvoice-!1 Creating another branch department login for a user and making it an Enterprise user!|EnterObject|UserBranchDepartment|UserName|Branch|Department|UserGroup|Is Department Access Department Admin User|Is Department Access Branch Admin User|Is Admin Branch Division|Is Admin Branch Company|Is Admin Branch Enterprise|Enter!|ID?|tomb|St Louis|Rental|Branch Manager|True|True|True|True|True|True|tomb3|EX: http:/fitnesssvr:8088/FrontPage.ProfitMaster.AccountsPayable.ApInvoice.VoidApInvoice-!1 Testing out a standard comments control on an entitySee if all Comments tab fields are there and then see if they are enabled!|Click Tab|Comments|!|Inspect Form Fields|BriefDescription|_vtlCommentType|_vtlPredefinedComment|ChkPredefinedComment|Comment|Test|General|False|Test Corp Comment|!|Check|that the field|BriefDescription|is visible|true|Check|that the field|_vtlCommentType|is visible|true|Check|that the field|_vtlPredefinedComment|is visible|true|Check|that the field|ChkPredefinedComment|is visible|true|Check|that the field|Comment|is visible|true|Make sure comments are enabled B-03538!|Check|that the field|BriefDescription|is enabled|true|Check|t