Skip to end of banner
Go to start of banner

2018-10-09 UI Testing Team Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

Attendees

Goals

  • Demo of work needed to improve BigTest bootstrapping process.  
  • Demo of generating code coverage for ui-users by Nightmare tests

Helpful information to review prior to meeting:

  • N/A



TimeItemWhoNotes
30 minDemo of BigTest bootstrapping changesWil and Jeffrey

1) Wil and Jeffrey moved a lot of BigTest bootstrap code to stripes-core. It will make configuration of UI module much easier. https://github.com/folio-org/stripes-core/pull/430

2) Smart components are is not a typical UI module. Wil explains his approach here: https://github.com/folio-org/stripes-smart-components/pull/297

15 minDemo of generating Nightmare code coverage reportEric Valuk

Eric demonstrated Nightmare tests that can generate code coverage report identical to BigTest because they both are using the same tool: https://istanbul.js.org/

As of right now, the is outstanding issue that coverage report is not being generated if tests are run against a platform.

30 minFree discussion
  1. ui-inventory was identified is #1 priority to build unit test code coverage. Jeffrey will bootstrap ui-inventory this week so that Zak can start building unit tests for this module.
  2. stripes-cli commands for bootstrapping BigTest should be finished by 10/12
  3. Coverage in SonarCloud vs Circle CI will be report different numbers for ui-eholdings. Need to configure SonarCloud to exclude the same files that are being excluded by Circle CI.
  4. ui-checkin and ui-myprofile have BigTest unit test and can be configured for SonarCloud reporting.
  5. eHoldings build in Jenkins will be running longer (2X) until parallel test execution is implemented.
  6. General discussion about long term plan for Nightmare tests. Eventually they will be phased out as individual module tests. We'll use them for integration testing only. BigTest will be used for unit tests.
  7. "Next Release" branch ( https://jenkins-aws.indexdata.com/job/folio-org/job/platform-complete/job/next-release/) should be used to build system for ui-module testing because it will be more stable than snapshot.

Action items

  • No labels