Key | Value |
---|---|
FileName | ./usr/share/doc/packages/ruby2.7-rubygem-minitest/History.rdoc |
FileSize | 64 |
MD5 | 092F3735B172F1FA56540F400A90271A |
SHA-1 | 38706AA0FFA91F2E4B3161D0B870A5B910694757 |
SHA-256 | 7872780327ED0C9B64FC2D0A5C75A735F05A792ADC4AD9855105FCF02E8A6B92 |
SSDEEP | 3:gCjCCA2PKeZSLVK+WKvGn:/dDshK/KvGn |
TLSH | T11BA0027103F725B96AC098287D59EE02B3044D0EBB167F4532DC85A6145C10762D5555 |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 452E37C06058D933BC7DFA89BAFB1A70 |
PackageArch | i586 |
PackageDescription | minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/unit is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/unit and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/unit is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. |
PackageName | ruby2.7-rubygem-minitest |
PackageRelease | 1.45 |
PackageVersion | 5.7.0 |
SHA-1 | CBFADD84A25F295316156E3FE4E0A7E9BEE9E3AF |
SHA-256 | EFB7B0DA0B30DE1E306BC8FD2CDE41828AA4B5B77971B3AF6B963157EA2E474B |
Key | Value |
---|---|
MD5 | 48E7BAE9FD3E1207AACD2D23F54E2312 |
PackageArch | i586 |
PackageDescription | minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/unit is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/unit and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/unit is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. |
PackageName | ruby2.7-rubygem-minitest |
PackageRelease | 1.42 |
PackageVersion | 5.7.0 |
SHA-1 | F022C680A8804CA51189A8C394FA49160995AE2E |
SHA-256 | AB5183E2D453398FB4E8D7C0242961772B77E2E4B1441AA6F8486092861BAC8C |