Skip to content

feat: Lumen test matrix #118

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.

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

Closed
wants to merge 24 commits into from
Closed

feat: Lumen test matrix #118

wants to merge 24 commits into from

Conversation

bishopb
Copy link

@bishopb bishopb commented Dec 10, 2021

Description of the change

Adds a test matrix for Lumen, similar to how is done for Laravel in #115. The failures here are all expected, owing to the incorrect handling of session. As a reminder, this pass is meant to document the current state of the integration: later passes will check master against the relevant versions.

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Maintenance
  • New release

Related issues

Checklists

Development

  • Lint rules pass locally
  • The code changed/added as part of this pull request has been covered with tests
  • All tests related to the changed code pass in development

Code review

  • This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
  • "Ready for review" label attached to the PR and reviewers assigned
  • Issue from task tracker has a link to this pull request
  • Changes have been reviewed by at least one other engineer

Bishop Bettini added 24 commits November 19, 2021 09:53
This is the basic operation: stand up the framework, configure
Rollbar within that framework, then invoke a log message. Rig
Rollbar so that logged messages get written to a file, that we
then check exists and contains the desired value.

Later iterations will add the specifics for each framework-version,
which may require multiple action files: the setup varies slightly
between framework and framework-version.
Never store secrets. Also, by pushing the secret definition into
the runner, we have more flexibility for choosing their value based
on branch conditions (eg, for testing certain behaviors of various
tokens).
The [docs][1] call for `4.*` and `2.*`, so we'll use those to align
with the exact documentation.

[1]:https://docs.rollbar.com/docs/laravel
Now we'll add them in one at a time, excluding or fixing the bad
combo.
Covers Laravel 5.6 through 8, on the appropriate PHP versions from
the 7.x series. Comments out a known failing combination of Laravel
5.5 and doesn't include the unlikely to work PHP 8 support.
Hunting down why failing on GitHub action but not local `act`.
The runner is removing leading zeroes, setting the value to '0'.
This failed locally, but it may have been a false negative.
Includes support for confirming the upstream version as well as
prototype for testing local when the branching is ready for that.
@bishopb bishopb marked this pull request as ready for review December 15, 2021 03:15
@bishopb bishopb requested a review from bxsx December 15, 2021 03:15
@bxsx
Copy link

bxsx commented Jan 10, 2022

The failures here are all expected, owing to the incorrect handling of session. As a reminder, this pass is meant to document the current state of the integration: later passes will check master against the relevant versions.

I understand the approach, but I believe that CI should never fail. It would be better to mark failed tests as skipped/ignored and backlog the failed results.

@bishopb bishopb closed this Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants