Versions Compared

Old Version 1

changes.mady.by.user Anton Emelianov (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Anton Emelianov (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees

Goals

  • Status of RTL/Jest implementation by team:
  1. Did team start working on RTL/Jest coverage. If no, when are you planning to start.
  2. Do you have any challenges with the knowledge on how to create these tests.
  3. Do you have Jenkins pipeline integration for these tests
  4. How do you track test coverage for RTL/Jest tests
  5. Do you use scratch dev environments to execute RTL/Jest tests before PR
  6. Do you have pipelines within Rancher  to execute RTL/Jest tests
  7. Describe problems/challenges that you are have with implementation of RTL/Jest tests
TimeItemWhoNotes
60 minFirebird
  1. Yes
  2. No
  3. Not sure
  4. Not sure
  5. No. Want to start. Anton to reach to Stanislav to help the team.
  6. No
  7. see the above 


eUsage ERM 
  1. No
  2. No
  3. Not integrated into Jenkins pipeline (need sample) Anton to find sample for Richard. Concord team has example.
  4. No, See above
  5. Team wants access to scratch environment. 
  6. No
  7. Just sample for pipeline and scratch system


Core Functional
  1. Zac wrote RTL test for Stripes-util
  2. No
  3. Added changes to Jenkins file but test didn't run. Need good instructions. Wiki page. Victor?
  4. No
  5. FE devs not using scratch env. yet. No help needed.
  6. No
  7. No


Spitfire
  1. Didn't start yet. Plan to start in sprint 106.
  2. Use new interactors. 
  3. Need help from Victor +wiki.  Anton to post link to sample jenkins job from Malconian.
  4. No
  5. Yes. Not running Jest tests against scratch env. Need documentation how to create pipelines in rancher.
  6. No. but want to build them themselves.
  7. No


Concorde
  1. data-export and  data-transfer-components have RTL tests. Soon to create tasks for other  modules. PO will set priorities.
  2. No
  3. Yes! 
  4. Team has both coverage reports in the pipeline
  5. Not using scratch env.  We need better docs how to do it.
  6. No
  7. No


ERM
  1. Started setting up RTL/Jest . Wrote sample tests. Sprint 104 and 105 will be used to transition to RTL tests.
  2. Need more knowledge on RTL API.  Victor to post links.
  3. No. Will use ui-data-export as a sample.
  4. No
  5. Need help to get started with scratch environments.
  6. No
  7. No.


Thunderjet
  1. Yes!  
  2. No
  3. Yes. ui-orders, ui-invoice, ui-finance, ui-receiving. Anton to check on teams modules.
  4. Yes.
  5. Tried to use scratch env. Anton to get together with the team to go over usage  scratch env. usage. Don't run RTL tests.
  6. No
  7. Team wants to have e-2e test to run against scratch env. It would be more useful.

Action items

  •