minitest
LevelDB
Our great sponsors
minitest | LevelDB | |
---|---|---|
10 | 27 | |
3,236 | 34,871 | |
0.6% | 1.2% | |
8.2 | 0.0 | |
9 days ago | about 1 month ago | |
Ruby | C++ | |
MIT License | BSD 3-clause "New" or "Revised" 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.
LevelDB
-
Codebases to read
I'm partial to how cleanly written https://github.com/google/leveldb is. It is a reasonable size to fully read & grok in not too long.
-
SQLite performance tuning: concurrent reads, multiple GBs and 100k SELECTs/s
Google didnt, thus Chrome started replacing sqlite with https://github.com/google/leveldb
-
Is there a lightweight, stable and embedded database library?
leveldb?
- Ask HN: What's the best source code you've read?
-
LevelDB VS ZoneTree - a user suggested alternative
2 projects | 22 Aug 2022
-
Open Source Databases in Go
goleveldb - Implementation of the LevelDB key/value database in Go.
-
Warp: Lightweight Multi-Key Transactions for Key-Value Stores
I don't know of any rule of English grammar that would lead to this interpretation. If you do, you should immediately write to the maintainers of these websites:
https://redis.com/nosql/key-value-databases/
https://www.mongodb.com/databases/key-value-database
https://aws.amazon.com/nosql/key-value/
https://etcd.io/docs/v3.4/learning/why/
https://riak.com/products/riak-kv/
-
Leveldb File Forensics
https://github.com/google/leveldb -- successfully compiled the tool. This tool seemed the most promising. I tried using the command:
- Ask HN: What are the best key-value self-hosted storage engines?
What are some alternatives?
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
Test::Unit - test-unit
MongoDB - The MongoDB Database
SQLite - Unofficial git mirror of SQLite sources (see link for build instructions)
RSpec - RSpec meta-gem that depends on the other components
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
LMDB - Read-only mirror of official repo on openldap.org. Issues and pull requests here are ignored. Use OpenLDAP ITS for issues.
CouchDB - Seamless multi-master syncing database with an intuitive HTTP/JSON API, designed for reliability
SQLite - Official Git mirror of the SQLite source tree
Apache Cassandra - Mirror of Apache Cassandra
libmdbx - One of the fastest embeddable key-value ACID database without WAL. libmdbx surpasses the legendary LMDB in terms of reliability, features and performance.
ClickHouse - ClickHouse® is a free analytics DBMS for big data