Please enable JavaScript.

Coggle requires JavaScript to display documents.

9. Fiori Testing (Integration Testing (OPA5 (OPA5 Configurations (sap.ui…

- - - - Arrange: Prepare for the test
      - Act: perform the actual action under test
      - Assert: compare the result of Act phase to the expected result
    - - Assert.equal(result, expected, Message)
      - Assert.ok(true_or_false_logic, "Message")
        
        nonempty string = PASSED
        
        0, null, NaN, empty string, and undefined = FAILED
    - - Stubs
        
        return objects that the actual execution of a function would
        return but without executing the actual code
      - Mocks
        
        define expectations on implementation of the code under test
        
        Expectations
        
        can be how many times an API is called
        
        which arguments are to be passed
        
        what exact values of arguments are to be passed, etc.
  - - - oController.getAge = sinon.stub().returns(45);
      - getAge(agr) always return 45 as the age
      - oController.calculateCost
        = sinon.stub().withArgs([‘3323234’, 2]).returns(330);
    - - sinon.mock(oObj).expects("method").atLeast(2).atMost(5);
      - oObj.method gets called at least twice else test will failed
- - - - organize all the testing code together ⇒ remove it before distribution.
      - create new folder "test"
        
        "test" contain all test code
      - create folder "unit" in "test"
        
        "unit" contain only unit test cases
      - files inside "unit" will reflect the structure of the application inside the "webapp"
      - create "controller" folder in "unit"
      - create a file with the same name as the controller name in "controller"
        
        load the original controller, which contains the code under test
    - - QUnit.module
        
        defines a module that can contain one or more test cases
      - QUnit.test
        
        define a test case
        
        QUnit.test("shown string", assert_function(assert))
        
        assert.strictEqual(testResult, "expectedResult", "String when test passed")
      - allTests.js
        
        Calling All Test Cases of the App
      - unitTests.qunit.html
        
        HTML Page That Launches All Unit Tests
        
        QUnit.start();
- - - - create "integration" in "test" folder
      - OPA Page
        
        in "integration/pages"
        
        JavaScript
        
        contains tests for each page in the application
        
        roughly pointing to an SAPUI5 view
        
        SAP Web IDE provides a wizard for creating an OPA page
        
        right-click on the project, and choose New > OPA Page
        
        AllJourneys.js
        
        include the new OPA pages
      - create "pages" in "integratopn" folder
      - OPA Journey
        
        a group of integration test definitions defined in an order
        
        stored directly under the "integration" folder
        
        Wizard: New > OPA Journey
        
        opaTest.qunit.html
        
        QUnit.start();
        
        includes all pages, journeys and
        OPA5 tests
      - Given = Arrange
      - When = Act
      - Then = Assert
    - - sap.ui.test.Opa5.extendConfig
      - arrangements
      - actions/assertions
      - viewNamespace
      - timeOut: seconds until which OPA5 will wait during a waitFor call
      - pollingInterval: milliseconds for the frequency
      - debugTimeout
      - executionDelay: slow down the running of integration tests
- - - - Create a folder "localService" under "webapp"
      - Add the OData service’s
        metadata into this "localServices"
      - use $metadata to get the metadata
    - - Right-click on the metadata.xml file, and select Edit Mock Data
      - Add Rows
        
        Delete Rows
        
        Generate Random Data
    - - "sap/ui/core/util/MockServer" class
    - - similar to index.html
        of the application but has additional code for initiating the mock data
      - mockServerIndex.html
        
        mockserver.init();
  - - - fires after the request processing of the mock server
    - - fired before the processing of the request