Establish Baseline CI Testing Across All Repositories#6
Open
opslevel[bot] wants to merge 1 commit intomainfrom
Open
Establish Baseline CI Testing Across All Repositories#6opslevel[bot] wants to merge 1 commit intomainfrom
opslevel[bot] wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change establishes a baseline continuous integration testing setup for the pager_duty-connection repository. The repository previously had CI configured but it only ran code linting (StandardRB) without any actual tests. This update adds a comprehensive test suite and CI workflow while preserving the existing linting workflow.
Changes Made
Added a complete testing infrastructure using Minitest, the standard Ruby testing framework. Created a test suite with 20 smoke tests that verify basic functionality including module/class definitions, version constants, connection initialization with various parameters, API method availability, and error class definitions. The tests ensure the library can be loaded and initialized correctly without requiring external API calls.
Configured a new GitHub Actions workflow that runs tests on multiple Ruby versions (2.7, 3.0, 3.1, 3.2) for both pull requests and pushes to the main/master branches. The workflow installs dependencies via Bundler and executes the test suite using Rake. Updated the Rakefile to define a test task and set it as the default task.
Added a CI status badge to the README that displays the current test status, and documented the testing approach with clear instructions on how to run tests locally. The existing StandardRB linting workflow remains unchanged and continues to function alongside the new test workflow.