qsar-report 0.0.2

data/test/data/qmrf_t8.xml

@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE QMRF PUBLIC "http://qmrf.sourceforge.net/qmrf.dtd" "qmrf.dtd">
+<QMRF author="Joint Research Centre, European Commission" contact="Joint Research Centre, European Commission" date="July 2007" email="JRC-IHCP-COMPUTOX@ec.europa.eu" name="(Q)SAR Model Reporting Format" schema_version="1.0" url="http://ihcp.jrc.ec.europa.eu/" version="1.3">
+<QMRF_chapters>
+<QSAR_identifier chapter="1" help="" name="QSAR identifier">
+<QSAR_title chapter="1.1" help="" name="QSAR identifier (title)"/>
+<QSAR_models chapter="1.2" help="" name="Other related models"/>
+<QSAR_software chapter="1.3" help="" name="Software coding the model">
+			
+      <software_ref idref="firstsoftware"/>
+</QSAR_software>
+</QSAR_identifier>
+<QSAR_General_information chapter="2" help="" name="General information">
+<qmrf_date chapter="2.1" help="" name="Date of QMRF"/>
+<qmrf_authors chapter="2.2" help="" name="QMRF author(s) and contact details">
+		
+      <author_ref idref="firstauthor"/>
+<author_ref idref="secondauthor"/></qmrf_authors>
+<qmrf_date_revision chapter="2.3" help="" name="Date of QMRF update(s)"/>
+<qmrf_revision chapter="2.4" help="" name="QMRF update(s)"/>
+<model_authors chapter="2.5" help="" name="Model developer(s) and contact details">
+		
+      <author_ref idref="modelauthor"/>
+</model_authors>
+<model_date chapter="2.6" help="" name="Date of model development and/or publication"/>
+<references chapter="2.7" help="" name="Reference(s) to main scientific papers and/or software package">
+
+      </references>
+<info_availability chapter="2.8" help="" name="Availability of information about the model"/>
+<related_models chapter="2.9" help="" name="Availability of another QMRF for exactly the same model"/>
+</QSAR_General_information>
+<QSAR_Endpoint chapter="3" help="" name="Defining the endpoint - OECD Principle 1">
+<model_species chapter="3.1" help="" name="Species"/>
+<model_endpoint chapter="3.2" help="" name="Endpoint">
+
+      </model_endpoint>
+<endpoint_comments chapter="3.3" help="" name="Comment on endpoint"/>
+<endpoint_units chapter="3.4" help="" name="Endpoint units"/>
+<endpoint_variable chapter="3.5" help="" name="Dependent variable"/>
+<endpoint_protocol chapter="3.6" help="" name="Experimental protocol"/>
+<endpoint_data_quality chapter="3.7" help="" name="Endpoint data quality and variability"/>
+</QSAR_Endpoint>
+<QSAR_Algorithm chapter="4" help="" name="Defining the algorithm - OECD Principle 2">
+<algorithm_type chapter="4.1" help="" name="Type of model"/>
+<algorithm_explicit chapter="4.2" help="" name="Explicit algorithm">
+<algorithm_ref idref="algorithms_catalog_1"/>
+<equation/>
+</algorithm_explicit>
+<algorithms_descriptors chapter="4.3" help="" name="Descriptors in the model">
+      
+      <descriptor_ref idref="descriptors_catalog_1"/>
+</algorithms_descriptors>
+<descriptors_selection chapter="4.4" help="" name="Descriptor selection"/>
+<descriptors_generation chapter="4.5" help="" name="Algorithm and descriptor generation"/>
+<descriptors_generation_software chapter="4.6" help="" name="Software name and version for descriptor generation" options="">
+				
+      <software_ref idref="software_catalog_2"/>
+</descriptors_generation_software>
+<descriptors_chemicals_ratio chapter="4.7" help="" name="Chemicals/Descriptors ratio"/>
+</QSAR_Algorithm>
+<QSAR_Applicability_domain chapter="5" help="" name="Defining the applicability domain - OECD Principle 3">
+<app_domain_description chapter="5.1" help="" name="Description of the applicability domain of the model"/>
+<app_domain_method chapter="5.2" help="" name="Method used to assess the applicability domain"/>
+<app_domain_software chapter="5.3" help="" name="Software name and version for applicability domain assessment">
+
+      <software_ref idref="software_catalog_3"/>
+</app_domain_software>
+<applicability_limits chapter="5.4" help="" name="Limits of applicability"/>
+</QSAR_Applicability_domain>
+<QSAR_Robustness chapter="6" help="" name="Internal validation - OECD Principle 4">
+<training_set_availability answer="Yes" chapter="6.1" help="" name="Availability of the training set"/>
+<training_set_data cas="Yes" chapter="6.2" chemname="Yes" formula="Yes" help="" inchi="Yes" mol="Yes" name="Available information for the training set" smiles="Yes"/>
+<training_set_descriptors answer="All" chapter="6.3" help="" name="Data for each descriptor variable for the training set"/>
+<dependent_var_availability answer="All" chapter="6.4" help="" name="Data for the dependent variable for the training set"/>
+<other_info chapter="6.5" help="" name="Other information about the training set"/>
+<preprocessing chapter="6.6" help="" name="Pre-processing of data before modelling"/>
+<goodness_of_fit chapter="6.7" help="" name="Statistics for goodness-of-fit"/>
+<loo chapter="6.8" help="" name="Robustness - Statistics obtained by leave-one-out cross-validation"/>
+<lmo chapter="6.9" help="" name="Robustness - Statistics obtained by leave-many-out cross-validation"/>
+<yscrambling chapter="6.10" help="" name="Robustness - Statistics obtained by Y-scrambling"/>
+<bootstrap chapter="6.11" help="" name="Robustness - Statistics obtained by bootstrap"/>
+<other_statistics chapter="6.12" help="" name="Robustness - Statistics obtained by other methods"/>
+</QSAR_Robustness>
+<QSAR_Predictivity chapter="7" help="" name="External validation - OECD Principle 4">
+<validation_set_availability answer="Yes" chapter="7.1" help="" name="Availability of the external validation set"/>
+<validation_set_data cas="Yes" chapter="7.2" chemname="Yes" formula="Yes" help="" inchi="Yes" mol="Yes" name="Available information for the external validation set" smiles="Yes"/>
+<validation_set_descriptors answer="All" chapter="7.3" help="" name="Data for each descriptor variable for the external validation set"/>
+<validation_dependent_var_availability answer="All" chapter="7.4" help="" name="Data for the dependent variable for the external validation set"/>
+<validation_other_info chapter="7.5" help="" name="Other information about the external validation set"/>
+<experimental_design chapter="7.6" help="" name="Experimental design of test set"/>
+<validation_predictivity chapter="7.7" help="" name="Predictivity - Statistics obtained by external validation"/>
+<validation_assessment chapter="7.8" help="" name="Predictivity - Assessment of the external validation set"/>
+<validation_comments chapter="7.9" help="" name="Comments on the external validation of the model"/>
+</QSAR_Predictivity>
+<QSAR_Interpretation chapter="8" help="" name="Providing a mechanistic interpretation - OECD Principle 5">
+<mechanistic_basis chapter="8.1" help="" name="Mechanistic basis of the model"/>
+<mechanistic_basis_comments chapter="8.2" help="" name="A priori or a posteriori mechanistic interpretation"/>
+<mechanistic_basis_info chapter="8.3" help="" name="Other information about the mechanistic interpretation"/>
+</QSAR_Interpretation>
+<QSAR_Miscelaneous chapter="9" help="" name="Miscellaneous information">
+<comments chapter="9.1" help="" name="Comments"/>
+<bibliography chapter="9.2" help="" name="Bibliography">
+				
+      <publication_ref idref="publications_catalog_1"/>
+</bibliography>
+<attachments chapter="9.3" help="" name="Supporting information">
+        
+        
+        
+        
+        
+        
+      <attachment_training_data/>
+<attachment_validation_data/>
+<attachment_documents/>
+</attachments>
+</QSAR_Miscelaneous>
+<QMRF_Summary chapter="10" help="" name="Summary (JRC QSAR Model Database)">
+<QMRF_number chapter="10.1" help="" name="QMRF number">To be entered by JRC</QMRF_number>
+<date_publication chapter="10.2" help="" name="Publication date">To be entered by JRC</date_publication>
+<keywords chapter="10.3" help="" name="Keywords">To be entered by JRC</keywords>
+<summary_comments chapter="10.4" help="" name="Comments">To be entered by JRC</summary_comments>
+</QMRF_Summary>
+</QMRF_chapters>
+<Catalogs>
+<software_catalog>
+<software contact="" description="" id="firstsoftware" name="" number="" url=""/>
+<software contact="" description="" id="software_catalog_2" name="" number="" url=""/>
+<software contact="" description="" id="software_catalog_3" name="" number="" url=""/>
+</software_catalog>
+<algorithms_catalog>
+<algorithm definition="" description="" id="algorithms_catalog_1" publication_ref=""/>
+</algorithms_catalog>
+<descriptors_catalog>
+<descriptor description="" id="descriptors_catalog_1" name="" publication_ref="" units=""/>
+</descriptors_catalog>
+<endpoints_catalog/>
+<publications_catalog>
+<publication id="publications_catalog_1" title="" url=""/>
+</publications_catalog>
+<authors_catalog>
+<author affiliation="" contact="" email="myauthor@myauthor.dom" id="firstauthor" name="Dr. My MyName" number="" url="http://myauthor.dom"/>
+<author affiliation="" contact="" email="" id="modelauthor" name="" number="" url=""/>
+<author id="secondauthor" name="Dr. Mysec MysecName" url="http://myauthor.dom" email="myauthor@myauthor.dom"/></authors_catalog>
+</Catalogs>
+</QMRF>

data/test/data/qprf-t6.json

@@ -0,0 +1,197 @@
+{
+  "meta": {
+    "description": "qprf report",
+    "title": "qprf report",
+    "qprf_version": "1.1",
+    "date": ""
+  },
+  "visible": true,
+  "singleCalculations": {
+    "Date": "2016/08/21",
+    "Disclaimer and Instructions": "Please fill in the fields of the QPRF with information about the prediction and the substance                                for which the prediction is made. The information that you provide will be used to facilitate                                considerations on the adequacy of the prediction (model result) in relation to a defined                                regulatory purpose.                                The adequacy of a prediction depends on the following conditions: a) the (Q)SAR model is                                scientifically valid: the scientific validity is established according to the OECD principles for                                (Q)SAR validation; b) the (Q)SAR model is applicable to the query chemical: a (Q)SAR is                                applicable if the query chemical falls within the defined applicability domain of the model; c)                                the (Q)SAR result is reliable: a valid (Q)SAR that is applied to a chemical falling within its                                applicability domain provides a reliable result; d) the (Q)SAR model is relevant for the                                regulatory purpose: the predicted endpoint can be used directly or following an                                extrapolation, possibly in combination with other information, for a particular regulatory                                purpose.                                A (Q)SAR prediction (model result) may be considered adequate if it is reliable and relevant,                                and depending on the totality of information available in a weight-of-evidence assessment                                (see Section 4 of the QPRF).",
+    "Time": "",
+    "Title": "My QPRF Report",
+    "Version": "2.1"
+  },
+  "arrayCalculations": {
+    "1. Substance": {
+      "colNames": [
+        "Title",
+        "Value"
+      ],
+      "values": {
+        "General": [
+          "Instructions",
+          "This section is aimed at defining the substance for which the (Q)SAR prediction is made."
+        ],
+        "1.1": [
+          "CAS number",
+          "7732-18-5"
+        ],
+        "1.2": [
+          "EC number",
+          "Report the EC number."
+        ],
+        "1.3": [
+          "Chemical name",
+          "Report the chemical names (IUPAC and CAS names)."
+        ],
+        "1.4": [
+          "Structural formula",
+          "Report the structural formula."
+        ],
+        "1.5 General": [
+          "Structure codes",
+          "Report available structural information for the substance, including the structure code used     to run the model. If you used a SMILES or InChI code, report the code in the corresponding field below.     If you have used any another format (e.g. mol file), please include the corresponding structural representation     as supporting information."
+        ],
+        "1.5 a.": [
+          "SMILES",
+          "Report the SMILES of the substance (indicate if this is the one used for the model prediction)."
+        ],
+        "1.5 b.": [
+          "InChI",
+          "Report the InChI code of the substance (indicate if this is the one used for the model prediction)."
+        ],
+        "1.5 c.": [
+          "Other structural representation",
+          "Indicate if another structural representation was used to generate the prediction.     Indicate whether this information is included as supporting information. Example: 'mol file used     and included in the supporting information'."
+        ],
+        "1.5 d.": [
+          "Stereochemical features",
+          "Indicate whether the substance is a stereo-isomer and consequently may have properties     that depend on the orientation of its atoms in space. Identify the stereochemical features that may affect the reliability     of predictions for the substance, e.g. cis-trans isomerism, chiral centres. Are these features encoded in the structural     representations mentioned above?"
+        ]
+      }
+    },
+    "2. General information": {
+      "colNames": [
+        "Title",
+        "Value"
+      ],
+      "values": {
+        "General": [
+          "Instructions",
+          "General information about the compilation of the current QPRF is provided in this section."
+        ],
+        "2.1": [
+          "Date of QPRF",
+          "Report the date of compilation of the QPRF. Example: “01 January 2007”."
+        ],
+        "2.2": [
+          "QPRF author and contact details",
+          "Report the contact details of the author of the QPRF."
+        ]
+      }
+    },
+    "3. Prediction": {
+      "colNames": [
+        "Title",
+        "Value"
+      ],
+      "values": {
+        "General": [
+          "Instructions",
+          "The information provided in this section will help to facilitate considerations on the     scientific validity of the model (as defined in the OECD Principles for the validation of (Q)SAR models)     and the reliability of the prediction. Detailed information on the model are stored in the corresponding     QMRF which is devised to reflect as much as possible the OECD principles. Remember that the QMRF and the     QPRF are complementary, and a QPRF should always be associated with a defined QMRF."
+        ],
+        "3.1 General": [
+          "Endpoint",
+          "(OECD Principle 1)"
+        ],
+        "3.1 a.": [
+          "Endpoint",
+          "Define the endpoint for which the model provides predictions (this information should correspond to the information provided in the QMRF under fields 3.2 and 3.3). Example: 'Nitrate radical degradation rate constant KNO3'."
+        ],
+        "3.1 b.": [
+          "Dependent variable",
+          "Report the dependent variable for which the model provides predictions including any transformations introduced for modelling purposes (note that this information should correspond to the information provided in the QMRF under field 3.5). Example: '-log (KNO3)'."
+        ],
+        "3.2 General": [
+          "Algorithm",
+          "(OECD Principle 2)"
+        ],
+        "3.2 a.": [
+          "Model or submodel name",
+          "Identify the model used to make the prediction and possibly report its name as stored in the corresponding QMRF; in the QMRF the model name is reported in the field QSAR identifier. Examples: “BIOWIN for Biodegradation”; “TOPKAT Developmental Toxicity Potential”. If applicable identify the specific submodel or algorithm applicable to the specific chemical Examples: 'BIOWIN '; 'TOPKAT Skin Irritation Acyclics (Acids, Amines, Esters) MOD v SEV Model'; 'ECOSAR esters model'."
+        ],
+        "3.2 b.": [
+          "Model version",
+          "Identify, where relevant, the version number and/or date of the model and submodel."
+        ],
+        "3.2 c.": [
+          "Reference to QMRF",
+          "Provide relevant information about the QMRF that stores information about the model     used to make the prediction. Possible useful pieces of information are: availability, source, reference number (if any)     of the QMRF. Examples: 'The corresponding QMRF named -BIOWIN for Biodegradation- has been downloaded from the JRC QSAR     Model Database'; 'The corresponding QMRF named -TOPKAT Skin Irritation Acyclics (Acids, Amines, Esters) MOD v SEV Model-    has been newly compiled'."
+        ],
+        "3.2 d.": [
+          "Predicted value (model result)",
+          "Report the predicted value (including units) obtained from the application of the model to the query chemical. For an expert system such as Derek for Windows, report the alert triggered together with the reasoning. Example: ' aromatic amine - mutagenicity, plausible'."
+        ],
+        "3.2 e.": [
+          "Predicted value (comments)",
+          "If the result is qualitative (e.g. yes/no) or semi-quantitative (e.g. low/medium/high),     explain the cut-off values that were used as the basis for classification. In reporting the predicted value, pay attention     to the transformations (e.g. if the prediction is made in log units, apply anti-logarithm function)."
+        ],
+        "3.2 f.": [
+          "Input for prediction",
+          "Specify what kind of input was used to generate the prediction (SMILES, mol file, graphical     interface etc). Please provide the structure code used to generate the prediction (unless already provided in section 1.5)."
+        ],
+        "3.2 g.": [
+          "Descriptor values",
+          "Where appropriate, report the values (experimental or calculated data) for numerical descriptors and indicate which values were used for making the prediction."
+        ],
+        "3.3 General": [
+          "Applicability domain",
+          "(OECD principle 3)"
+        ],
+        "3.3 a.": [
+          "Domains",
+          "Discuss whether the query chemical falls in the applicability domain of the model as defined in the corresponding     QMRF (section 5 of QMRF, Defining the applicability domain - OECD Principle 3). If additional software/methods were used to assess     the applicability domain then they should also be documented in this section. Include a discussion about: i. descriptor domain     ii. structural fragment domain (e.g., discuss whether the chemical contains fragments that are not represented in the model     training set) iii. mechanism domain (discuss whether the chemical is known or considered to act according to the mechanism of     action associated with the used model) iv. metabolic domain, if relevant"
+        ],
+        "3.3 b.": [
+          "Structural analogues",
+          "List the structural analogues that are present in the training or test sets, or accessible from other sources (in this case you should explain how the structural analogue was retrieved1) and why they are considered analogues). For each analogue, report the CAS number, the structural formula, the SMILES code, and the source (e.g., training set, test set or other source). For an expert system (like Derek for Windows or TOPKAT), the example compounds or structurally related analogues with their experimental data should be provided here."
+        ],
+        "3.3 c.": [
+          "Considerations on structural analogues",
+          "Discuss how predicted and experimental data for analogues support the     prediction of the chemical under consideration. "
+        ],
+        "3.4": [
+          "The uncertainty of the prediction (OECD principle 4)",
+          "If possible, comment on the uncertainty of the prediction for     this chemical, taking into account relevant information (e.g. variability of the experimental results). "
+        ],
+        "3.5": [
+          "The chemical and biological mechanisms according to the model underpinning the predicted result (OECD principle 5)",
+          "Discuss the mechanistic interpretation of the model prediction for this specific chemical. For an expert system based on     structural alerts (e.g. Derek for Windows, OncologicTM) the rationale for the structural alert fired should be provided."
+        ]
+      }
+    },
+    "4. Adequacy (Optional)": {
+      "colNames": [
+        "Title",
+        "Value"
+      ],
+      "values": {
+        "General": [
+          "Instructions",
+          "The information provided in this section might be useful, depending on the reporting needs     and formats of the regulatory framework of interest.     This information aims to facilitate considerations about the adequacy of the (Q)SAR prediction (result)     estimate. A (Q)SAR prediction may or may not be considered adequate ('fit-for-purpose'), depending on     whether the prediction is sufficiently reliable and relevant in relation to the particular regulatory     purpose. The adequacy of the prediction also depends on the availability of other information, and is     determined in a weight-of-evidence assessment."
+        ],
+        "4.1": [
+          "Regulatory purpose",
+          "Explain the regulatory purpose for which the prediction described     in Section 3 is being used."
+        ],
+        "4.2": [
+          "Approach for regulatory interpretation of the model result",
+          "Describe how the predicted result     is going to be interpreted in light of the specific regulatory purpose (e.g. by applying an algorithm or     regulatory criteria). This may involve the need to convert the units of the dependent variable (e.g. from     log molar units to mg/l). It may also involve the application of another algorithm, an assessment factor,     or regulatory criteria, and the use or consideration of additional information in a weight-of-evidence assessment. "
+        ],
+        "4.3": [
+          "Outcome",
+          "Report the interpretation of the model result in relation to the defined regulatory purpose."
+        ],
+        "4.4": [
+          "Conclusion",
+          "Provide  an assessment of whether the final result is considered adequate for a regulatory     conclusion, or whether additional information is required (and, if so, what this additional information should be)."
+        ]
+      }
+    }
+  },
+  "figures": {
+  },
+  "_id": ""
+}

data/test/qmrf-report.rb

@@ -0,0 +1,74 @@
+require_relative "setup.rb"
+
+class QMRFReportTest < MiniTest::Test
+
+  def test_0_self
+    puts "MiniTest #{self.class} start OK"
+  end
+
+  def test_1_base
+    report = OpenTox::QMRFReport.new
+    assert report
+    assert_kind_of(OpenTox::QMRFReport, report)
+  end
+
+  def test_2_validate
+    report = OpenTox::QMRFReport.new
+    assert_empty report.validate
+  end
+
+  def test_3_write_some_values
+    report = OpenTox::QMRFReport.new
+    report.Value "QSAR_title", "My QSAR Title"
+    report.Value "QSAR_models", "My QSAR Model"
+    assert_equal report.Value("QSAR_title"), "My QSAR Title"
+    assert_equal report.Value("QSAR_models"), "My QSAR Model"
+    refute_equal report.Value("QSAR_title"), "lazar"
+  end
+
+  def test_4_write_check
+    report = OpenTox::QMRFReport.new
+    report.Value "QSAR_title", "My QSAR Title"
+    report.Value "QSAR_models", "My QSAR Model"
+    assert_equal report.to_xml, File.read(File.join(File.join(DATA_DIR, "qmrf_t4.xml")))
+  end
+
+  def test_5_write_catalog
+    report = OpenTox::QMRFReport.new
+    report.change_catalog :software_catalog, :firstsoftware, {:name => "lazar", :contact => "in-silico toxicology gmbh", :url => "https://lazar.in-silico.ch", :description => "lazar toxicity predictions"}
+    assert "in-silico toxicology gmbh", report.get_catalog_value(:software_catalog, :firstsoftware, :contact)
+    assert "lazar", report.get_catalog_value(:software_catalog, :firstsoftware, :name)
+    assert "https://lazar.in-silico.ch", report.get_catalog_value(:software_catalog, :firstsoftware, :url)
+    assert "lazar toxicity predictions", report.get_catalog_value(:software_catalog, :firstsoftware, :description)
+  end
+
+  def test_6_check_catalog_exists
+    report = OpenTox::QMRFReport.new
+    assert_raises RuntimeError do
+      report.catalog_exists? :noexist_catalog
+    end
+    assert report.catalog_exists? :software_catalog
+  end
+  
+  def test_7_write_alot
+    report = OpenTox::QMRFReport.new
+    report.Value "QSAR_title", "My QSAR Title"
+    report.Value "QSAR_models", "My QSAR Model"
+    report.change_catalog :software_catalog, :firstsoftware, {:name => "lazar", :contact => "in-silico toxicology gmbh", :url => "https://lazar.in-silico.ch", :description => "lazar toxicity predictions"}
+    report.change_catalog :publications_catalog, :publications_catalog_1, {:title => "MyName M (2016) My Publication Title, QSAR News, 10, 14-22", :url => "http://myqsarnewsmag.dom"}
+    report.change_catalog :publications_catalog, :publications_catalog_2, {:title => "MyName M (2016) My Second Publication Title, Hornblower, 101ff.", :url => "http://hornblower.dom"}
+    assert_equal report.to_xml, File.read(File.join(File.join(File.dirname(__FILE__),"data/qmrf_t7.xml")))
+    report.change_catalog :publications_catalog, :publications_catalog_3, {:title => "MyName M (2016) My Third Publication Title, Somewhereelse, 43f.", :url => "http://somewhereelse.dom"}
+    refute_equal report.to_xml, File.read(File.join(File.join(DATA_DIR, "qmrf_t7.xml")))
+  end
+
+  def test_8_ref_catalog_entry
+    report = OpenTox::QMRFReport.new
+    report.change_catalog :authors_catalog, :firstauthor, {:name => "Dr. My MyName", :url => "http://myauthor.dom", :email => "myauthor@myauthor.dom"}
+    report.ref_catalog :qmrf_authors, :authors_catalog, :firstauthor
+    report.change_catalog :authors_catalog, :secondauthor, {:name => "Dr. Mysec MysecName", :url => "http://myauthor.dom", :email => "myauthor@myauthor.dom"}
+    report.ref_catalog :qmrf_authors, :authors_catalog, :secondauthor
+    assert_equal report.to_xml, File.read(File.join(File.join(DATA_DIR, "qmrf_t8.xml")))
+  end
+
+end

data/test/qprf-report.rb

@@ -0,0 +1,52 @@
+require_relative "setup.rb"
+
+class QMRFReportTest < MiniTest::Test
+
+  def test_0_self
+    puts "MiniTest #{self.class} start OK"
+  end
+
+  def test_1_base
+    report = OpenTox::QPRFReport.new
+    assert report
+    assert_kind_of(OpenTox::QPRFReport, report)
+    assert report.to_json
+    assert report.to_html
+    assert report.pretty_json
+  end
+
+  def test_2_md
+    report = OpenTox::QPRFReport.new
+    assert report.to_html
+  end
+
+  def test_3_get_Title
+    report = OpenTox::QPRFReport.new
+    assert_equal report.Title, "QSAR Prediction Reporting Format (QPRF)"
+  end
+  
+  def test_4_set_Values
+    report = OpenTox::QPRFReport.new
+    report.Title = "My Test Title"
+    report.Version = "12"
+    assert_equal report.Title, "My Test Title"
+    assert_equal report.Version, "12"
+    #puts report.to_html
+  end
+
+  def test_5_get_11
+    report = OpenTox::QPRFReport.new
+    report.Value "1.1", "7732-18-5"
+    assert_equal report.Value("1.1"), "7732-18-5"
+  end
+
+  def test_6_set_more_Values
+    report = OpenTox::QPRFReport.new
+    report.Title = "My QPRF Report"
+    report.Version = "2.1"
+    report.Date = "2016/08/21"
+    report.Value "1.1", "7732-18-5"
+    assert_equal report.pretty_json, File.read(File.join(DATA_DIR,'qprf-t6.json'))
+  end
+
+end