rules_pycross
mutant
| rules_pycross | mutant | |
|---|---|---|
| 2 | 5 | |
| 51 | 1,928 | |
| - | - | |
| 9.2 | 8.2 | |
| 4 days ago | 6 days ago | |
| Starlark | Ruby | |
| Apache License 2.0 | Nonstandard |
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.
rules_pycross
- Show HN: Morgan – PyPI Mirror for Restricted/Offline Environments
-
An ex-Googler's guide to dev tools
I also think it is partly as the tooling is not there yet - especially in the typical case when a project depends on lots of external dependencies.
I am looking forward to new set of bazel rules being worked on for eg. https://github.com/aspect-build/rules_js and https://github.com/jvolkman/rules_pycross which will makes it more idiomatic to work with existing language ecosystems.
mutant
-
An ex-Googler's guide to dev tools
There's a pretty good Ruby gem I've used for this before:
https://github.com/mbj/mutant
-
Code coverage vs mutation testing.
You should only really care about mutation testing if your code coverage is relatively high. If your code coverage is 20% then mutation testing should not be your priority. We use mutation testing (mutant for Ruby, pitest for Java). mutant is pretty hassle-free but only works when running under MRI so if you use jruby you are out of luck. pitest was far less easy to integrate.
- Mutant – Automated code reviews via mutation testing – semantic code coverage
- Automated code reviews via mutation testing - semantic code coverage.
-
Semantic blind spot in Ruby case statement
mutant shows redundant semantics, why we'd like to reduce them is perhaps better explained at https://github.com/mbj/mutant#what-is-mutant
What are some alternatives?
clusterfuzz - Scalable fuzzing infrastructure.
Ruby-JMeter - A Ruby based DSL for building JMeter test plans
rules_js - High-performance Bazel rules for running Node.js tools and building JavaScript projects
Spring - Rails application preloader
resolvelib - Resolve abstract dependencies into concrete ones
Parallel Tests - Ruby: 2 CPUs = 2x Testing Speed for RSpec, Test::Unit and Cucumber
simpleindex
vcr - Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.
subpar - Subpar is a utility for creating self-contained python executables. It is designed to work well with Bazel.
rspec-side_effects - RSpec extension for checking the side effects of your specifications.
pypickup - Creates a local PyPI mirror that works offline
timecop - A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.