@Test
public void hasField_Width() throws Exception {
  String filename = "documentUnderTest.pdf";
  String fieldname = "Title of 'someField'"; 
  int allowedDeltaForMillis = 2;
  int allowedDeltaForPoints = 0;
  
  AssertThat.document(filename)
            .hasField(fieldname)
            .withWidth(450) // default is POINTS
            .withWidth(450, POINTS, allowedDeltaForPoints)
            .withWidth(159, MILLIMETERS, allowedDeltaForMillis)
  ;
}

In the previous example, 'width' refers to width as the internal property of the acro field. Since this is expressed in the unit points, PDFUnit takes the values for the methods withWidth(..) and withHeight(..) by default in points. To prevent rounding errors when converting points into millimeters, the third parameter of those methods determines the allowable difference between the expected size and the actual size.

@Test
public void hasHugeFormat() throws Exception {
  String filename = "documentUnderTest.pdf";
  int heightMM = 1117;
  int widthMM = 863;
  DocumentFormat formatMM = new DocumentFormatMillis(widthMM, heightMM);
  
  AssertThat.document(filename)
            .hasFormat(formatMM)
  ;
}

When page formats are created, the constants MILLIMETERS and POINTS cannot be used. Use the classes DocumentFormatMillis and DocumentFormatPoints instead.

Error messages print both the original unit and millimeters. For example, if the width in the last example had been set to 111 POINTS, PDFUnit would have shown the following error message:

Wrong page format in 'physical-map-of-the-world-1999_1117x863mm.pdf' on page 1. 
Expected: 'height=1117.60, width=39.16 (as 'mm', converted from unit 'points')', 
but was:  'height=1117.60, width=863.60 (as 'mm')'.