[FOLIO-1882] UI Regression tests failures for Q1 platform-core release Created: 20/Mar/19  Updated: 03/Jun/20  Resolved: 26/Mar/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: John Malconian Assignee: Zak Burke
Resolution: Done Votes: 0
Labels: q1-2019
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File ui-test-stalled.txt    
Issue links:
Blocks
blocks FOLIO-1869 Q1 platform-core platform-complete re... Closed
Sprint: Core: F - Sprint 59, Core: F - Sprint 60
Development Team: Prokopovych

 Description   

UI Regression/Integration tests fail on a Q1 release build. The build is currently based on the q1-2019-rc branch of platform-core.

Latest test results are here: https://jenkins-aws.indexdata.com/job/folio-org/job/platform-core/view/change-requests/job/PR-250/10/UI_20Regression_20Test_20Report/

The FOLIO instance these tests were run against is available at: http://platform-core-250-10.aws.indexdata.com/



 Comments   
Comment by John Malconian [ 20/Mar/19 ]

I was able to resolve the failing inventory module test 'should search for contributor: Huntley, Henry Veel' by including a larger inventory data set in the build. So that brings the count down to 31 failing tests.

Latest test report: https://jenkins-aws.indexdata.com/job/folio-org/job/platform-core/view/change-requests/job/PR-250/11/UI_20Regression_20Test_20Report/

Latest release build: http://platform-core-250-11.aws.indexdata.com/

Comment by John Malconian [ 20/Mar/19 ]

Test updates for the q1 release in platform-core should be merged to the branch q1-2019-rc. This will trigger a build of a new FOLIO instance as well as a UI integration test against the instance.

Comment by Zak Burke [ 21/Mar/19 ]

I merged the updates from #snapshot into #q1-2019-rc and got down to 10 failures when I ran from my local clone against platform-core-250-11. 4 passed when I ran them individually rather than as part of the suite, and 2 I think are just related to the different dataset on this instance.

That leaves 4 true failures. All are related to loan rules and renewal, all are known problems on the #snapshot branch too. I'll keep cracking away at this.

Comment by Zak Burke [ 21/Mar/19 ]

Fascinating; 10 tests failed in the Jenkins build. Lots of overlap with my local run among the loan renewal failures, but not so much otherwise: https://jenkins-aws.indexdata.com/job/folio-org/job/platform-core/view/change-requests/job/PR-250/lastBuild/UI_20Regression_20Test_20Report/

Comment by Zak Burke [ 21/Mar/19 ]

Digging a little deeper into the two codex failures, the response's resultInfo.diagnostics array is totally empty, which implies to me that the codex isn't configured correctly. On a junk query from my local stripes instance without configuring the kb, for example, I see

{
  "instances" : [ ],
  "resultInfo" : {
    "totalRecords" : 0,
    "facets" : [ ],
    "diagnostics" : [ {
      "source" : "mod-codex-ekb-1.3.0-SNAPSHOT.89",
      "code" : "500",
      "message" : "Invalid url: null/rm/rmaccounts/null/titles?searchfield=titlename&selection=selected&resourcetype=all&searchtype=advanced&search=asdfasdfasdfff*&offset=1&count=30&orderby=titlename"
    }, {
      "source" : "mod-codex-inventory-1.5.0-SNAPSHOT.67",
      "code" : "200",
      "recordCount" : 0,
      "query" : "(title = asdfasdfasdfff*) and (ext.selected = true) sortby title"
    } ]
  }
}

but here I see

{
  "instances" : [ ],
  "resultInfo" : {
    "totalRecords" : 0,
    "facets" : [ ],
    "diagnostics" : [ ]
  }
}
Comment by John Malconian [ 21/Mar/19 ]

Hmm. mod-codex-ekb-1.3.0-SNAPSHOT.89 is not included in the "core" platform.

Comment by John Malconian [ 21/Mar/19 ]

I notice that when I run the UI tests against http://platform-core-250-17.aws.indexdata.com, I get 12 failures and test-regression doesn't exit. Output attached.

Comment by John Malconian [ 21/Mar/19 ]

The two Codex search failures are definitely legit. It appears that the mod-codex-inventory module is not loaded. Will attempt to fix and report back.

Comment by John Malconian [ 21/Mar/19 ]

Codex search failures have been resolved. The latest build is available at: http://platform-core-250-27.aws.indexdata.com

Comment by John Malconian [ 21/Mar/19 ]

Just FYI - Best way to test against this build:

git clone https://github.com/folio-org/platform-core
git checkout q1-2019-rc
yarn install 
yarn test-regression --uiTest.username diku_admin --uiTest.password admin --show --url http://platform-core-250-27.aws.indexdata.com
Comment by John Malconian [ 26/Mar/19 ]

Zak Burke After merging your test changes to q1-2019-rc in platform-core, there are four failures. The good news is that the tests exit properly now.

https://jenkins-aws.indexdata.com/job/folio-org/job/platform-core/view/change-requests/job/PR-262/1/UI_20Regression_20Test_20Report/

Latest test instance is http://platform-core-262-1.aws.indexdata.com built from PR-262.

Feel free to run additional tests against that instance for additional troubleshooting.

Comment by Zak Burke [ 26/Mar/19 ]

Details under STRIPES-607; the failures for the snapshot branch are the same as for the q1-2019-rc branch.

Generated at Thu Feb 08 23:16:35 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.