Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

create automated performance testing environment

Description

A living document describing the approach has been created during a session in Durham and is located here:

https://docs.google.com/document/d/1MiF4N3ot3ewT8j9_jer6_br5ekOpXMrMEJR93WWPALA/edit

Environment

None

Potential Workaround

None

Attachments

1
  • 04 Jun 2018, 02:51 PM

Checklist

hide

TestRail: Results

Activity

Show:

Hongwei JiJuly 25, 2018 at 2:50 PM

it pulls the latest code from snapshot-stable automatically every time. Can you elaborate the "clear upgrade process"?

Jakub SkoczenJuly 25, 2018 at 2:42 PM

What is left here to make sure we can use the environment to track performance regressions and address them. We need a clear upgrade process, is it implemented?

John MalconianJuly 9, 2018 at 6:21 PM

Thanks, . You are correct about the graphs. I've scheduled the job to be run daily.

Hongwei JiJuly 6, 2018 at 6:53 PM

, I believe the Performance graphs need at least two successful builds to show the trend. As for the job frequencies, I have been running it only once a day in our environment.

John MalconianJuly 6, 2018 at 6:11 PM

After some modifications to FOLIO Jenkins and the configuration in the repository, I'm able to get a successful run in FOLIO Jenkins.

https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/

I've merged branch https://folio-org.atlassian.net/browse/FOLIO-1245#icft=FOLIO-1245 into master.

Outstanding:

  • It appears that the Performance graphs are not populated. Not sure why this is.

  • How do we want to run and use this job? Daily? How will it be reviewed?

Done

Details

Assignee

Reporter

Labels

Priority

Development Team

Prokopovych

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 15, 2018 at 9:26 AM
Updated November 12, 2018 at 2:24 PM
Resolved July 9, 2018 at 6:21 PM
TestRail: Cases
TestRail: Runs

Flag notifications