crytic

Mutation testing framework testing mutation-testing hacktoberfest
1.0.0 released

CircleCI

crytic

Crytic, pronounced /ˈkrɪtɪk/, is a mutation testing framework for the crystal programming language. Mutation testing is a type of software testing where specific statements in the code are changed to determine if test cases find this defect.

Crytic is in a very early state of development. It is not very clever, making it slow as well.

Blog posts

Introducing crytic - mutation testing in crystal-lang

Installation

Add this to your application's shard.yml:

development_dependencies:
  crytic:
    github: hanneskaeufler/crytic

After shards install, this will place the crytic executable into the bin/ folder inside your project.

Usage

Crytic will only mutate statements in one file, let's call that our subject. You must also provide a list of test files to be executed in order to find the defects.

./bin/crytic --subject src/blog/pages/archive.cr spec/blog_spec.cr

Development

TODO

Contributing

  1. Fork it (https://github.com/hanneskaeufler/crytic/fork)
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Run tests locally with crystal spec
  4. Commit your changes (git commit -am 'Add some feature')
  5. Push to the branch (git push origin my-new-feature)
  6. Create a new Pull Request

Contributors

crytic:
  github: hanneskaeufler/crytic
  version: ~> 1.0.0
License MIT
Crystal 0.25.1

Authors

Dependencies 1

  • diff~hanneskaeufler oprypin/unified-diff
    {'branch' => 'oprypin/unified-diff', 'github' => 'hanneskaeufler/crystal-diff'}

Development Dependencies 2

  • ameba
    {'github' => 'veelenga/ameba'}
  • coverage
    {'github' => 'anykeyh/crystal-coverage'}

Dependents 2

Last synced .
search fire star recently