File: readme.md

package info (click to toggle)
ruby-sus-fixtures-benchmark 0.2.1-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 116 kB
  • sloc: ruby: 244; makefile: 4
file content (49 lines) | stat: -rw-r--r-- 1,895 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# Sus::Fixtures::Benchmark

Provides fixtures for sus for running benchmarks.

[![Development Status](https://github.com/socketry/sus-fixtures-benchmark/workflows/Test/badge.svg)](https://github.com/socketry/sus-fixtures-benchmark/actions?workflow=Test)

## Installation

``` bash
bundle add sus-fixtures-benchmark
```

## Usage

Please see the [project documentation](https://socketry.github.io/sus-fixtures-benchmark/) for more details.

## Releases

Please see the [project releases](https://socketry.github.io/sus-fixtures-benchmark/releases/index) for all releases.

### v0.2.1

  - Fix links and add context.

### v0.2.0

  - Added `exactly(count)` method to `Sus::Fixtures::Benchmark::Repeats` which returns an `Exactly` instance for fixed-count benchmarking.

### v0.1.0

  - Added `Sus::Fixtures::Benchmark::Repeats` which is not an integer, but an instance that allows the block to be executed multiple times until the benchmark converges.

## Contributing

We welcome contributions to this project.

1.  Fork it.
2.  Create your feature branch (`git checkout -b my-new-feature`).
3.  Commit your changes (`git commit -am 'Add some feature'`).
4.  Push to the branch (`git push origin my-new-feature`).
5.  Create new Pull Request.

### Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the [Developer Certificate of Origin](https://developercertificate.org/). This ensures that all contributions are properly licensed and attributed.

### Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.