minitest
Aruba
Our great sponsors
minitest | Aruba | |
---|---|---|
10 | 1 | |
3,242 | 950 | |
0.6% | 0.3% | |
8.2 | 7.4 | |
13 days ago | 16 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
minitest
-
Test Driving a Rails API - Part Two
In this part, we’ll set up our testing environment so that we can test our Rails API using minitest with minitest/spec. We’ll look at the differences between traditional style unit tests and spec-style tests, or specs. I’ll demonstrate why you should use minitest-rails. We’ll look at using rack-test for testing our API. We’ll even create our own generator to generate API specs.
-
Where can I learn to deliver a proper solution?
I forgot to mention that reading code is also a good way to learn how to write code, it's like inspiration. Check repos of some gems you like. For example sidekiq https://github.com/sidekiq/sidekiq/tree/main/lib/sidekiq Or minitest https://github.com/minitest/minitest/tree/master/lib/minitest
-
I_suck_and_my_tests_are_order_dependent
All through GitHub.
1. From https://github.com/rails/rails/blob/6ffb29d24e05abbd9ffe3ea9..., click "Blame" on the header bar over the file contents.
2. Scroll down to the line and click on the commit in the left column.
3. Scroll down to the file that removed the line from its previous file, activesupport/lib/active_support/test_case.rb.
4. Click the three-dots menu in that file's header bar and select "View file".
5. Click "History" in the header bar of the contributors, above the file contents.
6. I guessed here at commit 281f488 on its message: "Use the method provided by minitest to make tests order dependent". There's a comment here that identified the problem which led to, and provided context for, the change in 6ffb29d.
The OP is from minitest's documentation, so to find the introduction in minitest, it's basically the same process.
1. Go to https://github.com/minitest/minitest.
2. Search the repo for the method name. Even just "i_suck" will match the commit.
3. Select the oldest commit in the results. That's a4553e2.
Minitest has a number of cheeky little judgments this [1][2], especially in the docs. That said they support all these things they don't prefer, within reason, and I appreciate that.
Minitest is also full of all sorts of weird peccadillos like being written in the "Seattle.rb style" and autloading files in all gems that match a certain path [3]. These are not how I'd structure a plugin framework or write code, but it works and the code is easy to understand and hack on. I've spent a lot of time reading the internals of minitest, monkey patching or generally torturing it in ways they probably wouldn't prefer but it's been a trustworthy, if judge-y, tool for years.
[1] https://github.com/minitest/minitest/blob/master/lib/minites...
[2] https://github.com/minitest/minitest/blob/master/lib/minites...
[3] https://github.com/minitest/minitest/blob/master/lib/minites...
You didn't follow the blame further.
First, the flag is provided by minitest. That commit is an implementation of the flag in Rails.
Second, 6ffb29d moved it to prevent Rails's test framework from setting it _by default_. 281f488[1] actually added it to Rails.
minitest/minitest#a4553e2[2] appears to have added the docstring and test case to minitest.
1: https://github.com/rails/rails/commit/281f488fffc176084bf77c...
2: https://github.com/minitest/minitest/commit/a4553e2e127072c9...
-
Minitest, we've been doing it wrong?
The new test convention is now "test/**/test_*.rb" instead of "test/**/*_test.rb". For example, Puma and Minitest are popular repositories using this naming pattern.
-
Ask HN: Codebases with great, easy to read code?
https://github.com/seattlerb/minitest really removed the FUD for me when i started learning Ruby and Rails. Its full of metaprogramming and fancy tricks but is also quite small, practical and informal in its style.
e.g. "assert_equal" is really just "expected == actual" at it's core but it uses both both a block param (a kind of closure) for composing a default message and calls "diff" which is a dumb wrapper around the system "diff" utility (horrors!). There is even some evolved nastiness in there for an API change that uses the existing assert/refute logic to raise an informative message. this is handled with a simple if and not some sort of complex hard-to-follow factory pattern or dependency injection misuse.
https://github.com/seattlerb/minitest/blob/master/lib/minite...
-
Ruby through the lens of Go
One of the things I love the most about Ruby is that it tends to coalesce around one or two really popular libraries. Rails is the big one obviously, but over time you see libraries designed for a particular purpose "winning" over other things. This includes things like linting/code analysis (Rubocop), authentication (Devise), testing (RSpec and Minitest) and more. The emphasis is on making something good great rather than making a lot of different good things.
Aruba
-
Ruby: "the best" language for general automation
Another tool I found was Aruba, written in Ruby, but the documentation is practically non-existent and it recommends using it with Cucumber. Even the examples inside are in a features folder. I refuse to use Cucumber…
What are some alternatives?
Test::Unit - test-unit
RSpec - RSpec meta-gem that depends on the other components
Capybara - Acceptance test framework for web applications
Cucumber - A home for issues that are common to multiple cucumber repositories
Pundit Matchers - A set of RSpec matchers for testing Pundit authorisation policies.
shoulda-matchers - Simple one-liner tests for common Rails functionality
Spinach - Spinach is a BDD framework on top of Gherkin.
Fix - Specing framework.
Fuubar - The instafailing RSpec progress bar formatter
Cutest - Isolated tests in Ruby.
Bacon - a small RSpec clone