Source code ch.16: Testing completeness

Source Code & Software Patents: A Guide to Software & Internet Patent Litigation for Attorneys & Experts
by Andrew Schulman (
Detailed outline for forthcoming book

Chapter 16: Testing completeness & responsiveness of source-code production

16.1 External tests for completeness & responsiveness

  • 16.1.1 Completeness
  • 16.1.2 Responsiveness to request
  • 16.1.3 Ensuring that the correct version of the code has been produced: see chapter 22 on comparing source code to the commercial product at issue; chapter 23 on source-code versions
  • 16.1.4 Matching source code to results of product reverse engineering
  • 16.1.5 Ongoing completeness testing

16.2 Internal tests for completeness

  • 16.2.1 Checking out- and in-links
  • 16.2.2 Recompilation

16.3 Is the code truly missing?

  • 16.3.1 “Missing” filenames that are really present
  • 16.3.2 “Missing” code that is really present; for example, don’t assume the code must be in a file with a given extension; the code may use non-standard extensions, or employ languages with which the examiner is not familiar e.g. *.coffee CoffeeScript and *.hbs Handlebars files used to generate JavaScript

16.4 Spoliation and “redacted” code, including e.g. “redacted” comments: see chapter 10


Print Friendly, PDF & Email