TestComplete Tutorial 5 - Testing Approaches in TestComplete

 

  1. Unit Testing: When we have to test only a particular part of the application, we will create the unit test. We can invoke implicit methods of the applications.
  2. White-Box Testing: We will use this when we have to test the application as per the access. This testing has been carried out with the access not higher than the user
  3. Functional Testing: When we have to test the form from the customer's point-of-view, like checking What the way does for every user action.
  4. Parallel Testing: It is used for testing the multiple subcomponents of the applications in parallel. It reduces the testing time.
  5. Load Testing: It is utilized to put the predetermined load on the application and check the response.
  6. Regression Testing: It is utilized for reusing the test on the project when modifications are made to the code. We can compare the latest results with the old results.

Comments

Post a Comment

Popular posts from this blog

TestComplete Tutorial 9 - Mouse Actions and Mouse Wheel Events

 TestComplete provides mouse actions and mouse wheel events . Mouse Actions To simulate clicks, double-clicks, dragging and hovering (hot-tracking) operations, each onscreen object provides the following methods: Click( ) -  Simulates a single click performed with the left mouse button. ClickR( ) -  Simulates a single click performed with the right mouse button. ClickM( ) -  Simulates a single click performed with the middle mouse button. DblClick( ) -  Simulates a double click performed with the middle mouse button. DblClickR( ) -  Simulates a double click performed with the middle mouse button. DblClickM( ) -  Simulates a double click performed with the middle mouse button. Drag( ) -  Simulates a dragging operation performed with the left mouse button. DragR( ) -  Simulates a dragging operation performed with the right mouse button. DragM( ) -  Simulates a dragging operation performed with the middle mouse button. HoverMouse( ) - ...
Read more

TestComplete Tutorial 19 - Adding Objects to the Name Mapping Repository

Image
You can add objects to the Name Mapping repository in several ways: Automatically  when recording and editing tests. Manually  from the screen or from the Object Browser. From scripts . Mapping Objects Automatically By default, TestComplete adds objects to the  Name Mapping  repository  automatically  when you – Record tests, Create  checkpoints , Add or edit keyword test operations. This behavior is controlled by the  Engines > Name Mapping > Map object names automatically   option of TestComplete: If you do not use the Name Mapping repository in your project, you can disable this option to prevent TestComplete from mapping objects. To enable or disable automatic name mapping Select  Tools > Options  from the TestComplete main menu. This will open the  Options  dialog. Select the  Engines > Name Mapping  category. Select or clear the  Map object names automatically  check box. Click  O...
Read more

TestComplete Tutorial 14 - Object identification criteria in Name Mapping

  The object identification criteria that the repository stores and that TestComplete uses to search for objects in the applications can be: Property-value pairs -  For example: ObjectType = Page, URL=http://example.com Conditional expressions -  For example: WndCaption = Open OR Select File Selectors  -  (for web and mobile applications) For web applications, it can be XPath expressions and CSS selectors, for example,  //input[@id='instasearch']  or  #instasearch . For mobile applications, it can be the object class name, accessibility identifier, or an XPath expression, for example,  XCUIElementTypeStatusBar  or  //*[@name="Orders"] . Extended search -  Search for an object on all the levels down the object hierarchy rather than just on the current level. Required child objects -  Search for an object that has specific child objects.
Read more