mutant 0.9.8 → 0.9.13

data/Rakefile

@@ -1,5 +0,0 @@
-# frozen_string_literal: true
-
-require 'devtools'
-
-Devtools.init_rake_tasks

data/config/devtools.yml

@@ -1,2 +0,0 @@
----
-unit_test_timeout: 10.0

data/config/reek.yml

@@ -1,138 +0,0 @@
----
-detectors:
-  Attribute:
-    enabled: false
-    exclude: []
-  BooleanParameter:
-    enabled: true
-    exclude: []
-  ClassVariable:
-    enabled: true
-    exclude: []
-  ControlParameter:
-    enabled: true
-    exclude:
-    - Mutant::Expression#match_length
-  DataClump:
-    enabled: true
-    exclude: []
-    max_copies: 2
-    min_clump_size: 2
-  DuplicateMethodCall:
-    enabled: false
-    exclude: []
-    max_calls: 1
-    allow_calls: []
-  FeatureEnvy:
-    enabled: false
-  # Buggy smell detector
-  IrresponsibleModule:
-    enabled: false
-    exclude: []
-  LongParameterList:
-    enabled: true
-    exclude:
-    - Mutant::Matcher::Method::Instance#self.build
-    - Mutant::Meta::Example::DSL # 3 vars
-    max_params: 2
-  LongYieldList:
-    enabled: true
-    exclude: []
-    max_params: 2
-  NestedIterators:
-    enabled: true
-    exclude:
-    - Mutant#self.singleton_subclass_instance
-    - Mutant::CLI#parse
-    - Mutant::Mutator::Node::Arguments#emit_argument_mutations
-    - Mutant::Mutator::Node::Resbody#mutate_captures
-    - Mutant::Mutator::Util::Array::Element#dispatch
-    - Mutant::Parallel::Master#run
-    - Mutant::RequireHighjack#self.call
-    - Mutant::Selector::Expression#call
-    - Parser::Lexer#self.new
-    max_allowed_nesting: 1
-    ignore_iterators: []
-  NilCheck:
-    enabled: false
-  RepeatedConditional:
-    enabled: true
-    exclude:
-    - Mutant::Mutator
-    - Mutant::Meta::Example::DSL
-    max_ifs: 1
-  TooManyConstants:
-    enabled: false
-  TooManyInstanceVariables:
-    enabled: true
-    exclude:
-    - Mutant::Mutator # 4 vars
-    - Mutant::Parallel::Master # 4 vars
-    - Mutant::Meta::Example::DSL # 4 vars
-    max_instance_variables: 3
-  TooManyMethods:
-    enabled: true
-    exclude:
-    - Mutant::CLI
-    - Mutant::Mutator::Node
-    - Mutant::Parallel::Master
-    max_methods: 10
-  TooManyStatements:
-    enabled: true
-    exclude:
-    - Mutant::CLI#add_debug_options
-    - Mutant::CLI#add_environment_options
-    - Mutant::Reporter::CLI::Printer::Config#run
-    - Mutant::Reporter::CLI::Printer::EnvProgress#run
-    - Mutant::Runner#run_driver
-    - Mutant::Zombifier::File#self.find
-    max_statements: 7
-  UncommunicativeMethodName:
-    enabled: true
-    exclude:
-    - Mutant::AST::Sexp#s
-    - Mutant::Mutation#sha1
-    reject:
-    - '/^[a-z]$/'
-    - '/[0-9]$/'
-    - '/[A-Z]/'
-    accept: []
-  UncommunicativeModuleName:
-    enabled: true
-    exclude: []
-    reject:
-    - '/^.$/'
-    - '/[0-9]$/'
-    accept: []
-  UncommunicativeParameterName:
-    enabled: true
-    exclude: []
-    reject:
-    - '/^.$/'
-    - '/[0-9]$/'
-    - '/[A-Z]/'
-    accept: []
-  UncommunicativeVariableName:
-    enabled: true
-    exclude: []
-    reject:
-    - '/^.$/'
-    - '/[0-9]$/'
-    - '/[A-Z]/'
-    accept: ['force_utf32']
-  UnusedParameters:
-    enabled: true
-    exclude: []
-  UtilityFunction:
-    enabled: true
-    exclude:
-    - Mutant::AST::Sexp#s
-    - Mutant::CLI#reporter
-    - Mutant::Integration::Null#call
-    - Mutant::Integration::Rspec#parse_example
-    - Mutant::Integration::Rspec#parse_expression # intentional, private
-    - Mutant::Meta::Example::Verification#format_mutations # intentional, private
-    - Mutant::Reporter::CLI::Format::Progressive#new_buffer
-    - Mutant::Reporter::CLI::Printer::StatusProgressive#object # False positive calls super
-    - Mutant::Repository::Diff#tracks? # intentional, private
-    - Mutant::Repository::Diff#within_working_directory? # intentional, private

data/config/rubocop.yml

@@ -1,205 +0,0 @@
-inherit_from: ../.rubocop.yml
-
-# Avoid parameter lists longer than five parameters.
-ParameterLists:
-  Max: 3
-  CountKeywordArgs: true
-
-# Avoid more than `Max` levels of nesting.
-BlockNesting:
-  Max: 3
-
-# Align with the style guide.
-CollectionMethods:
-  Enabled: true
-  PreferredMethods:
-    collect:  'map'
-    inject:   'reduce'
-    find:     'detect'
-    find_all: 'select'
-
-AccessModifierIndentation:
-  Enabled: false
-
-# Limit line length
-LineLength:
-  Max: 120
-
-# Disable documentation checking until a class needs to be documented once
-Documentation:
-  Enabled: false
-
-# Permit
-#
-#     boolean_check? or fail
-#
-# Reject
-#
-#     if foo or bar
-#       ...
-#     end
-AndOr:
-  EnforcedStyle: conditionals
-
-# Do not favor modifier if/unless usage when you have a single-line body
-IfUnlessModifier:
-  Enabled: false
-
-# Allow case equality operator (in limited use within the specs)
-CaseEquality:
-  Enabled: false
-
-# Constants do not always have to use SCREAMING_SNAKE_CASE
-ConstantName:
-  Enabled: false
-
-# Not all trivial readers/writers can be defined with attr_* methods
-TrivialAccessors:
-  Enabled: false
-
-# Allow empty lines around class body
-EmptyLinesAroundClassBody:
-  Enabled: false
-
-# Allow empty lines around module body
-EmptyLinesAroundModuleBody:
-  Enabled: false
-
-# Allow empty lines around block body
-EmptyLinesAroundBlockBody:
-  Enabled: false
-
-# Allow multiple line operations to not require indentation
-MultilineOperationIndentation:
-  Enabled: false
-
-# Prefer String#% over Kernel#sprintf
-FormatString:
-  EnforcedStyle: percent
-
-# Use square brackets for literal Array objects
-PercentLiteralDelimiters:
-  PreferredDelimiters:
-    '%':  '{}'
-    '%i': '[]'
-    '%q': ()
-    '%Q': ()
-    '%r': '{}'
-    '%s': ()
-    '%w': '[]'
-    '%W': '[]'
-    '%x': ()
-
-# Use %i[...] for arrays of symbols
-SymbolArray:
-  Enabled: true
-
-# Prefer #kind_of? over #is_a?
-ClassCheck:
-  EnforcedStyle: kind_of?
-
-# Do not prefer double quotes to be used when %q or %Q is more appropriate
-Style/RedundantPercentQ:
-  Enabled: false
-
-# Allow a maximum ABC score
-Metrics/AbcSize:
-  Max: 21.02
-
-Metrics/BlockLength:
-  Exclude:
-  - 'spec/**/*.rb'
-  - 'mutant.gemspec'
-
-# Buggy cop, returns false positive for our code base
-NonLocalExitFromIterator:
-  Enabled: false
-
-# To allow alignment of similar expressions we want to allow more than one
-# space around operators:
-#
-# let(:a) { bar    + something }
-# let(:b) { foobar + something }
-#
-SpaceAroundOperators:
-  Enabled: false
-
-# We use parallel assignments with great success
-ParallelAssignment:
-  Enabled: false
-
-# Allow additional specs
-ExtraSpacing:
-  AllowForAlignment: true
-
-# Buggy
-FormatParameterMismatch:
-  Enabled: false
-
-# Different preference
-SignalException:
-  EnforcedStyle: semantic
-
-# Do not use `alias`
-Alias:
-  EnforcedStyle: prefer_alias_method
-
-# Do not waste my horizontal or vertical space
-Layout/FirstArrayElementIndentation:
-  Enabled: false
-
-# Prefer
-#
-#     some_receiver
-#       .foo
-#       .bar
-#       .baz
-#
-# Over
-#
-#     some_receiver.foo
-#                  .bar
-#                  .baz
-MultilineMethodCallIndentation:
-  EnforcedStyle: indented
-
-# Prefer `public_send` and `__send__` over `send`
-Send:
-  Enabled: true
-
-Layout/HashAlignment:
-  EnforcedColonStyle: table
-  EnforcedHashRocketStyle: table
-Layout/EmptyLineAfterGuardClause:
-  Enabled: false
-Layout/SpaceInsideArrayLiteralBrackets:
-  Enabled: false
-Lint/BooleanSymbol:
-  Enabled: false
-Lint/InterpolationCheck:
-  Enabled: false
-Lint/MissingCopEnableDirective:
-  Enabled: false
-Lint/UnifiedInteger:
-  Enabled: false
-Naming/FileName:
-  Enabled: false
-Style/AccessModifierDeclarations:
-  Enabled: false
-Style/CommentedKeyword:
-  Enabled: false
-Style/MixinGrouping:
-  Enabled: false
-Style/RaiseArgs:
-  Enabled: false
-Style/RescueStandardError:
-  Enabled: false
-Style/StderrPuts:
-  Enabled: false
-# suggesting single letter variablesl bah
-Naming/RescuedExceptionsVariableName:
-  Enabled: false
-# false positive on private keywords
-Layout/IndentationWidth:
-  Enabled: false
-

data/config/yardstick.yml

@@ -1,2 +0,0 @@
----
-threshold: 100

data/docs/commercial-support.md

@@ -1,14 +0,0 @@
-# Commercial Support
-
-Mutant offers only community support.
-
-Commercial license customers are entited to priority support via email.
-
-## Priority Support
-
-Covers 1 incident per quarter, with a max response time of 7 days.
-Scope is limited to mutant not the application or infrastructure.
-
-For support email [Markus Schirp](mailto:mbj@schirp-dso.com?subject=Mutant%20Support).
-Please email using the same domain as the roiginal license email or explain
-your connection to the license.

data/docs/concurrency.md

@@ -1,39 +0,0 @@
-Concurrency
-===========
-
-By default, mutant will test mutations in parallel by running up
-to one process for each core on your system. You can control the
-number of processes created using the `-j/--jobs` argument.
-
-Mutant forks a new process for each mutation to be tested to prevent side
-affects in your specs and the lack of thread safety in integrations from
-impacting the results.
-
-Database
---------
-
-If the code under test relies on a database, you may experience problems
-when running mutant because of conflicting data in the database. For
-example, if you have a test like this:
-
-```ruby
-resource = MyModel.create!(...)
-expect(MyModel.first.name).to eql(resource.name)
-```
-
-It might fail if some other test wrote a record to the `MyModel` table
-at the same time as this test was executed. (It would find the MyModel
-record created by the other test.) Most of these issues can be fixed
-by writing more specific tests. Here is a concurrent safe version of
-the same test:
-
-```
-resource = MyModel.create!(...)
-expect(MyModel.find_by_id(m.id).name).to eql(resource.name)
-```
-
-An alternative is to try wrapping each test into an enclosing transaction.
-
-Note that some databases, SQLite in particular, are not designed for
-concurrent access and will fail if used in this manner. If you are
-using SQLite, you should set the `--jobs` to 1.

data/docs/incremental.md

@@ -1,76 +0,0 @@
-# Incremental mutation testing
-
-Incremental mutation testing allows you to significantly speed up mutation
-analysis, via skipping over subjects that are not changed.
-
-This is an explicit trade off, often worth the downsides.
-
-## Motivation
-
-Despite all efforts in setting up a project for maximum mutation testing
-efficiency, running a full pass over all available subjects is not always
-desired. On building your branches on CI, and during local commit stage, its
-instead more efficient to scope the Mutant run to everything that was
-touched in the current branch / commit. The working set of subjects.
-
-For not having to manually keep track of the working set, the `--since` option
-allows you to specify a git reference point. Mutant will automatically subset all
-available subjects to the ones that where touched since the reference point.
-
-## Usage
-
-Use the `--since git-reference` flag to enable automatic filtering of the
-matched subjects to the ones that have a line changed since the reference
-point.
-
-Internally mutant will use the semantics of `git diff git-reference` to
-determine which subjects have changes. A subject is selected by this mechanism
-when `git diff` reports a hunk that overlaps with the current subjects line
-range.
-
-## Example
-
-On a branch, executing:
-
-```
-mutant --since master 'ProjectNamespace*'
-```
-
-Will run mutation testing against all subjects that have a direct source code
-since the `master` branch. Assuming your project has 100 subjects, and you
-touched 2 of them in your branch: Mutant will only select these 2 subjects for
-mutation testing.
-
-## Recommended use
-
-Use incremental for any project where a full pass does not fit within acceptable
-round trip times for the human mind.
-
-A small 200 loc gem, should probably never use it. Typically its the local per
-developer environment that should use incremental first. On CI its recommended
-to stay with the full pass as long as possible and switch to incremental mode
-when the CI cycle time gets too annoying.
-
-In addition, once using incremental its recommended to run a full pass as a
-nightly job.
-
-Incremental is also a good mode to retrofit mutation testing into a legacy
-project.
-
-Good selectors for reference points are `HEAD~1` (the previous commit) or
-`master` (the integration branch).
-
-## Limitations
-
-Mutant only triggers incremental subject selection for *direct* code changes.
-It'll currently not select subjects that where indirectly changed.
-
-Counter examples:
-
-* A change to a constant that results in a behavior change of a subject will
-  not trigger that subject to be selected.
-* A change to a subject A that causes another subject B to change in behavior,
-  will not select subject B.
-
-These limitations may be removed in future versions of mutant, work on more
-fine grained tracing is underway.