I_suck_and_my_tests_are_order_dependent

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • PopRuby - Clothing and Accessories for Ruby Developers
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • Ruby on Rails

    Ruby on Rails

    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

    minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking.

    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.

  • PopRuby

    PopRuby: Clothing and Accessories for Ruby Developers. Fashion meets Ruby! Shop our fun Ruby-inspired apparel and accessories designed to celebrate the joy and diversity of the Ruby community.

  • React

    The library for web and native user interfaces.

  • Chef

    Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale

    my contribution: public_method_that_only_deep_merge_should_use

    https://github.com/chef/chef/blob/68dd5f42273f19bc5975c0dc8e...

    that was 9 years ago and it was code smell that things were broken apart incorrectly and at some point i rewrote it so that wasn't necessary -- but sometimes you just gotta move the ball down the field, even if you don't get a first down.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts