The unit tests are currently out of date. The examples actually provide a decent test suite for log4r. But the unit tests are still very important because of bounds-checking and a quicker turnaround for bug discovery. The unit files need to be converted to the new 'test/unit' paradigm.
Because Log4r dynamically defines constants according to user preferences, the unit testing can't all be done in one instance of ruby. It is planned to use popen to run each test that needs a clean ruby instance.
The logs/ directory is where these tests dump generated log files.
FAQs
Unknown package
We found that log4r-color demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.
