Key | Value |
---|---|
FileName | ./usr/share/gems/gems/minitest-5.3.1/lib/minitest/spec.rb |
FileSize | 7266 |
MD5 | 22E1C2D07864BDE8A76F988E71C0379A |
SHA-1 | 05512714DD06A885CDD262C573DC9BC90E1F39CF |
SHA-256 | 9C86E0FACAD776D79531DFE3BBDE5F08ED8C9C2F382BE3A270AC42FA42AEA12E |
SSDEEP | 192:+XZfYynLEqXz6R4mGTWCsX0g3Zwc3g3Pu3K48b0c2gdym2ru9HBfOzIIy:sZfjqR9GTWCMHXKcyb0pO9HBfOzfy |
TLSH | T17AE1411B035330BE5152EA728CD5B80ABF1AD1BB93D20B6878AEC0900F4655A5AF76F5 |
hashlookup:parent-total | 9 |
hashlookup:trust | 95 |
The searched file hash is included in 9 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 3B207641E21B1DEB2BEA7FC68A7EC13D |
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 | 2.fc21 |
PackageVersion | 5.3.1 |
SHA-1 | 3A8BE041381A1C016B2BF6968BE96208FC834925 |
SHA-256 | 64EB715959C786CC1B9F04DFE1502D35BA9584805F0D8FFAE741E5C0B0399051 |
Key | Value |
---|---|
MD5 | C15A8FE209DDB22FAD09CD822848CE63 |
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 | 3.fc23 |
PackageVersion | 5.3.1 |
SHA-1 | B5D803045673B3DA52B82C63C69D615D9662C4F2 |
SHA-256 | D4B9411CCC9D907D6E5306B713B727AF9D25440C8AF08C4EB72697108BF68663 |
Key | Value |
---|---|
MD5 | F5F11D2707AEC28CF0DCBC9B5CF86A62 |
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 | 2.fc21 |
PackageVersion | 5.3.1 |
SHA-1 | 6514A7AEE6CA73778A7115BD8C5B303B6B02563B |
SHA-256 | 756FC9F1986C364F6047F5015D0C37F4E7EDD404BFCDCDF4311A581BDEB53D42 |
Key | Value |
---|---|
MD5 | B69BF8614577C0E5A66D70E8DD98BC80 |
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 | 2.fc21 |
PackageVersion | 5.3.1 |
SHA-1 | ECB5DF78A854FF9F91D89D9F01CA6C9B5FD3A6B4 |
SHA-256 | 9D72A0AF5D6FD30EC9B135F937DA76DC3899FB10A4C798A18958E7A62B472157 |
Key | Value |
---|---|
MD5 | 11DD45C9E174C13D04FBF0B6CA4CCDCA |
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 | 3.fc23 |
PackageVersion | 5.3.1 |
SHA-1 | 8B24AE1F216967DE3F28F519DA971F5CE68A98ED |
SHA-256 | 80E4CB7416D294ABFA1B608A49F2F366B143790C4BEAEE0B6E916B8AFFC47583 |
Key | Value |
---|---|
MD5 | 46D4751E7D9050AA91EBB3CFD617AA47 |
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 | 2.fc21 |
PackageVersion | 5.3.1 |
SHA-1 | 454728C4B3BDEBCF068DB2BE64E38D0FD1F6499B |
SHA-256 | A5F74219AAFEB50A05D6B0E2986450BE84A30B63064AC3C429A6162192279E4C |
Key | Value |
---|---|
MD5 | 6496C26AE729C15EADB0E15500900C84 |
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 | 3.fc23 |
PackageVersion | 5.3.1 |
SHA-1 | F6B3A137ADC6B6EFAB49135BCAFF1ED91116DAC9 |
SHA-256 | 3B077B97EE0ADC5C3E45CA8C4ADED41DFBEB2E9C5CC974EBBA9D644EDF6E5C47 |
Key | Value |
---|---|
MD5 | 2827058ED6AEC9C2C527BD0BF501752D |
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 | 2.fc21 |
PackageVersion | 5.3.1 |
SHA-1 | E85100B363BFCE6B68AB537F41D3E1C6B405E31B |
SHA-256 | 54C9B28D83E41004BD1BC9F025C6616CE6F4BE8BAB6C21277174ED14176E88A4 |
Key | Value |
---|---|
MD5 | 2F4BC734B125D077B51916B01D94A15E |
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 | 2.fc21 |
PackageVersion | 5.3.1 |
SHA-1 | 423D6E56DA1A380B9E2EB1D73F6B8C77809DED90 |
SHA-256 | 7E4CB28BCE264BD12D3FB5883DAB31860F345E0FD9D979FBF866C999636806DA |