Meta testing is the ability to test a function without having to 
    provide its parameter values.
    Those values will be generated, based on semantic naming of parameters, as 
    introduced by package 'wyz.code.offensiveProgramming'.
    Value generation logic can be completed with your own data types 
    and generation schemes. This to meet your most specific requirements and to 
    answer to a wide variety of usages, from general use case to very specific
    ones.
    While using meta testing, it becomes easier to generate stress test 
    campaigns, non-regression test campaigns and robustness test campaigns, as 
    generated tests can be saved and reused from session to session. 
    Main benefits of using 'wyz.code.metaTesting' is ability to discover valid 
    and invalid function parameter combinations, ability to infer valid 
    parameter values, and to provide smart summaries that allows you to focus
    on dysfunctional cases.

Allows to turn standard R code into offensive programming code. 
    Provides code instrumentation to ease this change and tools to assist and 
    accelerate code production and tuning while using offensive programming code 
    technics. 
    Should improve code robustness and quality. Function calls can be easily 
    verified on-demand or in batch mode to assess parameter types and length 
    conformities. 
    Should improve coders productivity as offensive programming reduces the code
    size due to reduced number of controls all along the call chain. 
    Should speed up processing as many checks will be reduced to one single check.

Allows to generate on-demand or by batch, any R documentation file,
    whatever is kind, data, function, class or package. It populates
    documentation sections, either automatically or by considering
    your input. Input code could be standard R code or offensive programming code. 
    Documentation content completeness depends on the type of code you use. With
    offensive programming code, expect generated documentation to be fully 
    completed, from a format and content point of view. With some standard R 
    code, you will have to activate post processing to fill-in any section that 
    requires complements. Produced manual page validity is automatically tested 
    against R documentation compliance rules. Documentation language 
    proficiency, wording style, and phrasal adjustments remains your job.