Parents (Total: 184)

The searched file hash is included in 184 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.1/packages//mips64//ruby-2.3.3.tgz
MD5	B46FB1DE41A7325E58690CEF7A0311D9
SHA-1	02231AF790DBC3B171A75054342F6914A157C8FF
SHA-256	CF3B1D81C3E6D44D2CB0208FC3763F27207F65FF05D382640D774BB056B1547D
SSDEEP	196608:TWe+IpdvwLUXuamGi8/dnOZcJv7ebXfSp+fPa7:TWDIpd4LUXuam/ciIv7ebXfO+fPE
TLSH	T171763341A4A4B1D19005D8376229B723633137D67EFAB9C76C1B3FA4A3D295CFD28D84

Key	Value
MD5	D6B68261E5211BD553035A2FA27A0BA2
PackageArch	x86_64
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-5_3_3
PackageRelease	lp151.1.6
PackageVersion	5.3.3
SHA-1	02E848812A695748DCF6678A42726FB20D7A326D
SHA-256	CDC4E7E22887A6CD44A5416E94DEF150F101F5678BE25CCBC0CF75BBB8F78D20

Key	Value
MD5	8D8338024035FAA7FDB3884BB1FCFA49
PackageArch	x86_64
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.5-rubygem-minitest-5_3_3
PackageRelease	1.2
PackageVersion	5.3.5
SHA-1	03E8B0CF03A036706C93D0ED1C3F98126214E249
SHA-256	B57BE5832A52BCB488CC8F3D947A20AEF1D0990060278E9B120C85AF65A8CE6A

Key	Value
MD5	68879A0C62EF5426347CF616A5F5C555
PackageArch	noarch
PackageDescription	minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. 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. 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.
PackageMaintainer	Fedora Project
PackageName	rubygem-minitest
PackageRelease	101.fc24
PackageVersion	5.8.4
SHA-1	0647A2E02119274C1663E0CDF4EB1C2951C5FE81
SHA-256	6B4337ED61EA60EE02F054D27C02B37890A621E9790C3DE5E23FDA85FA0D98B3

Key	Value
MD5	CFB3B87B317982109F84EBF164A73AC5
PackageArch	x86_64
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-5_3_3
PackageRelease	lp153.1.13
PackageVersion	5.3.5
SHA-1	079A0FBDB6198A7152809EC4F8809264E1E457D3
SHA-256	CFE160E48B0F02A53FBAF83729512E1DC3C5B7574C0B35AC90DE9734BFB57CE2

Key	Value
MD5	A0DB97BAF62D81AAA8B44228F379C64E
PackageArch	x86_64
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	ruby3.1-rubygem-minitest-5_3_3
PackageRelease	1.63
PackageVersion	5.3.3
SHA-1	07E2DF512D88F9636966D34B22318A387F50BCF3
SHA-256	C763FDF79AEEDE3CE852FD3EFE19A1D4BCE5D72AF7325B888A12A180619F6340

Key	Value
MD5	BA15758037A746A58E59F643251E22D9
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	ruby3.1-rubygem-minitest-5_3_3
PackageRelease	1.63
PackageVersion	5.3.5
SHA-1	09C5385FDF0ED4A8197E65EDC8FAAEDE2FE60069
SHA-256	3E9C8064DC3EF9B022CF6CFBE980E1BDBBC2FB5A3CE0D115C808EAC411868BAB

Key	Value
MD5	BDFBB99F749E481275684B1847DAED0A
PackageArch	x86_64
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.6-rubygem-minitest-5_3_3
PackageRelease	lp151.1.6
PackageVersion	5.3.5
SHA-1	0AEBED713FB3C67D3A1056CB3CBF715356E189D2
SHA-256	B500B49CAAC169B29AE2A86EB3C6F37ED6C4A68DFF1DBF17F147A3D008B1F00B

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.1/packages//arm//ruby-2.3.3.tgz
MD5	DCC69C1531BB6C9E815B0C905B0C770B
SHA-1	0B3235A2976B64BE5E9F2160F86385F5907D7F50
SHA-256	770F4187AE58711640D8548B2DCAD5BD18A881E074FF39381695FE66717F8B0F
SSDEEP	196608:7eT4oiMUaYYBIZKeQWHod3+wTPTwvlsFcX7ebXfSp+fPa0:R3ireBoE8PilsFcX7ebXfO+fPP
TLSH	T12376339D0AFEDC41F090B61B9622B9124D04369F88A2ED91F42054F953B21BD7A7BDF3

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.3/packages//mips64el//ruby-2.3.6p0.tgz
MD5	7847F4888A4943CA66408446AB228921
SHA-1	0E120A6A89E561339620B0D1EFBC399383D60461
SHA-256	22DBD19A739A856A18287DDF76A47F1F983F2DDD7F67D6466199162FCB1452B7
SSDEEP	196608:DUNbrvMfvwLqYVk5MKiUwxAqYcOTtXsAADKSp+fPaB:bQLqTMKjwxFYBtXtADKO+fPy
TLSH	T15D763311459EE72CE2BCB09AF87F4931B57C925DCCBB98C9B14928A90F26DF08917874