com.itextpdf.test.annotations.type Documentation Differences

iText 8.0.2 Overview Package Class Text Changes Statistics Help

Generated by
JDiff

PREV PACKAGE NEXT PACKAGE FRAMES NO FRAMES

com.itextpdf.test.annotations.type Documentation Differences

This file contains all the changes in documentation in the package com.itextpdf.test.annotations.type as colored differences. Deletions are shown ~~like this~~ , and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a tag will cause all subsequent paragraphs to be displayed differently.

 
  
 Class IntegrationTest
  

  

  
   Tests that cover more functionality than a simple Unit Test. Contrary to Unit Tests, they don't use mocked objects but real objects. These tests are intended to check end-to-end functionality of a feature. 
    For example, if a test creates a Document, manipulates it, writes the result to disk, and then compares the file with a reference document, then it is definitely not a Unit Test but most likely an Integration Test.
      @author Amedee Van Gasse
    
   
  
 Class PerformanceTest
  

  

  
   Performance Tests generate performance metrics: speed, memory usage, disk space,... 
    A Performance Test may repeat the same (or similar) test cases a lot, and may compare the metrics with metrics of a previous version.
      @author Amedee Van Gasse
    
   
  
 Class SampleTest
  

  

  
   Sample Tests give a Short, Self Contained, Correct, Example and can be used as documentation for end users.
     @author Amedee Van Gasse
   
   
  
 Class SlowTest
  

  

  
   Tests that can take longer than a couple of milliseconds to run. These tests can be excluded by a build tool that wants to a fast test of the code, for example only Unit Tests.
     @author Amedee Van Gasse
   
   
  
 Class UnitTest
  

  

  
   Unit Tests are used to check individual units of source code. A unit test will only use the Testing Framework and the individual unit that is being tested, but does not depend on any other functionality of the Software Under Test. 
    A simple rule to determine if you have written a unit test: if your test produces a PDF file and uses the CompareTool to verify it with a sample file, then it is not a unit test. 
    Typically a unit test will run very fast.
      @author Amedee Van Gasse