It is important to keep the test code concise and with as little duplication as possible. Here you are have 15 lines of code to get a single package in Data, the code is duplicated below with a small change. The details about `_packageMap` entry are not important for this test, since all the test needs is one arbitrary package in Data. The test code should express this intent without distracting the reader with unimportant details.

The usual approach is to use Test Data Builders for that. For the first test, you would use

```js
it('reports one package', function() {
  var registryData = givenDataWithSinglePackageVersion();
  // etc.
});
```
because the test doesn't care about package name or version.

The next test does care about package name and version in this test, because it deletes this specific version. And since tests should not depend on magic strings defined elsewhere, we want to pass name & version as parameters to the data builder.

```js
it('deletes the package', function(done) {

  var registryData = givenDataWithSinglePackageVersion('test-pkg', '0.0.1');
  registryData.deletePackage('test-pkg', '0.0.1', function() {
    // etc.
  });
});
```

Writing tests this way makes it clear what is important for the test (to have one package) and what is not (path to package, etc.). All information required to understand what is being tested is captured in the test code and there is no extra "noise".