Details

    • Type: Testing
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Sprint:
      LIMA | #15 | Mar03-Mar24, LIMA | #16 | Mar24-Apr14

      Description

      Background:

      See https://loop.liferay.com/home/-/loop/feed/20994964 for more details.

      As airports around the world are tightening up on their policies to prevent the influx of disease by introducing aggressive sanitization initiatives, stricter quarantine measures, comprehensive coverage and extensive testing, so too are we going to be doing the same to prevent regressions from happening in CI.

      With the forthcoming implementation of ci:forward, we need to be aggressively maintaining and extending ci:test:relevant. This means ALL tests in the module will be run anytime ci:test:relevant is run and will need to pass in the future workflow.

      This task is meant to document all tasks the Lima team needs to do in order to get our tests and suites to a point where we are ready for ci:forward.

      Tasks:

      First, assign one of the tickets below to yourself. This will scope your analysis to one app.

      Flaky Test Analysis

      3/17 vs. 3/18 Comparison
      3/18 vs. 3/19 Comparison
      3/17 vs. 3/19 Comparison

      We'll scope backend and poshi flaky test analysis to the last three builds in

       ci:test:lima 

      In each of the comparisons, please analyze:

      • FAILED > PASSED
      • PASSED > FAILED
      • PASSED > BLOCKED
      • BLOCKED TO PASSED to detect flaky tests

      For any tests for apps not run in ci:test:lima, analyze the following upstream master builds:

      3/16 vs. 3/17 Comparison
      3/17 vs. 3/18 Comparison
      3/16 vs. 3/18 Comparison
      1. Analyze one of the components below (organized by module)
      2. Add any flaky tests in the description of the appropriate subtask below and include a link to each failure
      3. Ignore flaky tests and link that ticket to the appropriate subtask below

      Test Fixes

      Attach all test fix tickets to the appropriate subtask below. Work on them as you normally would

      Backend Tests

      • File a bug ticket and link to the appropriate subtask below

      After all tickets linked to subtasks below are completed, then the subtask can be closed. A closed subtask means that tests running this app are 100% green in CI.

        Attachments

        1.
        Analyze and update files for test.properties change LPS-110630 Technical Testing Closed Austin Chiang  
        2.
        Analyze and stabilize Adaptive Media LPS-110631 Technical Testing Closed Yvonne Han  
        3.
        Analyze and stabilize Announcements LPS-110632 Technical Testing Closed Yvonne Han  
        4.
        Analyze and stabilize Blogs LPS-110633 Technical Testing Closed Yvonne Han  
        5.
        Analyze and stabilize Bulk LPS-110634 Technical Testing Closed Yvonne Han  
        6.
        Analyze and stabilize Comments LPS-110635 Technical Testing Closed Jeremy Chen  
        7.
        Analyze and stabilize Depot LPS-110636 Technical Testing Closed Jeremy Chen  
        8.
        Analyze and stabilize Document Library LPS-110637 Technical Testing Closed Jeremy Chen  
        9.
        Analyze and stabilize Google Drive/Microsoft One Drive LPS-110638 Technical Testing Closed Yvonne Han  
        10.
        Analyze and stabilize Image Editor LPS-110639 Technical Testing Closed Yvonne Han  
        11.
        Analyze and stabilize Item Selector LPS-110640 Technical Testing Closed Yvonne Han  
        12.
        Analyze and stabilize Knowledge Base LPS-110641 Technical Testing Closed Austin Chiang  
        13.
        Analyze and stabilize Content Page Review LPS-110642 Technical Testing Closed Jeremy Chen  
        14.
        Analyze and stabilize SEO LPS-110643 Technical Testing Closed Yvonne Han  
        15.
        Analyze and stabilize Mentions LPS-110644 Technical Testing Closed Yvonne Han  
        16.
        Analyze and stabilize Message Boards LPS-110645 Technical Testing Closed Jeremy Chen  
        17.
        Analyze and stabilize Microblogs LPS-110646 Technical Testing Closed Jeremy Chen  
        18.
        Analyze and stabilize Notifications LPS-110647 Technical Testing Closed Jeremy Chen  
        19.
        Analyze and stabilize Ratings LPS-110648 Technical Testing Closed Beck Liu  
        20.
        Analyze and stabilize Sharing LPS-110649 Technical Testing Closed Beck Liu  
        21.
        Analyze and stabilize Social LPS-110650 Technical Testing Closed Beck Liu  
        22.
        Analyze and stabilize Wiki LPS-110651 Technical Testing Closed Beck Liu  

          Activity

            People

            Assignee:
            austin.chiang Austin Chiang
            Reporter:
            austin.chiang Austin Chiang
            Recent user:
            Rubén Heras
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package