Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat(testing): use candidate versions of pepr in E2E tests when testing new functionality #1157

Draft
wants to merge 16 commits into
base: main
Choose a base branch
from
Draft

feat(testing): use candidate versions of pepr in E2E tests when testing new functionality #1157

wants to merge 16 commits into from

Conversation

samayer12
Copy link
Collaborator

Description

Demo work that simulates a "breaking change" to Pepr that would usually have to be merged to main before running in E2E tests found in pepr-excellent-examples.

End to End Test:
(See Pepr Excellent Examples)

Related Issue

Fixes #1109

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

@codecov Codecov
Copy link

codecov bot commented Sep 19, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.87%. Comparing base (ade478d) to head (af3b32f).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1157   +/-   ##
=======================================
  Coverage   85.87%   85.87%           
=======================================
  Files          27       27           
  Lines        1126     1126           
  Branches      231      231           
=======================================
  Hits          967      967           
  Misses        157      157           
  Partials        2        2

@samayer12 samayer12 changed the title feature(testing): Use candidate versions of pepr in E2E tests when testing new functionality feat(testing): Use candidate versions of pepr in E2E tests when testing new functionality Sep 19, 2024
@samayer12 samayer12 changed the title feat(testing): Use candidate versions of pepr in E2E tests when testing new functionality feat(testing): use candidate versions of pepr in E2E tests when testing new functionality Sep 19, 2024
@samayer12 samayer12 force-pushed the 1109-use-pepr-dist branch 2 times, most recently from db5dddf to b30222f Compare September 19, 2024 21:19
@samayer12 samayer12 mentioned this pull request Sep 19, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jeff-mccoy jeff-mccoy Awaiting requested review from jeff-mccoy jeff-mccoy will be requested when the pull request is marked ready for review jeff-mccoy is a code owner

@cmwylie19 cmwylie19 Awaiting requested review from cmwylie19 cmwylie19 will be requested when the pull request is marked ready for review cmwylie19 is a code owner

@btlghrants btlghrants Awaiting requested review from btlghrants btlghrants will be requested when the pull request is marked ready for review btlghrants is a code owner

@schaeferka schaeferka Awaiting requested review from schaeferka schaeferka will be requested when the pull request is marked ready for review schaeferka is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
Pepr Project Board
Status: 🆕 New
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

excellent examples pull in Pepr dist folder to test new api functionality
1 participant
@samayer12