diff --git a/test/manager/__snapshots__/manager-docs.spec.js.snap b/test/manager/__snapshots__/manager-docs.spec.js.snap
deleted file mode 100644
index e67b226338dc5e78bca664bc8e1ebf32325f0b68..0000000000000000000000000000000000000000
--- a/test/manager/__snapshots__/manager-docs.spec.js.snap
+++ /dev/null
@@ -1,159 +0,0 @@
-// Jest Snapshot v1, https://goo.gl/fbAQLP
-
-exports[`manager readmes has same questions for all managers 1`] = `
-Array [
- "ansible",
- "bazel",
- "buildkite",
- "bundler",
- "cargo",
- "circleci",
- "composer",
- "docker-compose",
- "dockerfile",
- "github-actions",
- "gitlabci",
- "gomod",
- "gradle",
- "gradle-wrapper",
- "kubernetes",
- "maven",
- "meteor",
- "npm",
- "nuget",
- "nvm",
- "pip_requirements",
- "pip_setup",
- "pipenv",
- "terraform",
- "travis",
-]
-`;
-
-exports[`manager readmes has same questions for all managers 2`] = `
-Array [
- "Name of package manager",
- "What language does this support?",
- "Does that language have other (competing?) package managers?",
- "What type of package files and names does it use?",
- "What [fileMatch](https://renovatebot.com/docs/configuration-options/#filematch) pattern(s) should be used?",
- "Is it likely that many users would need to extend this pattern for custom file names?",
- "Is the fileMatch pattern likely to get many \\"false hits\\" for files that have nothing to do with package management?",
- "Can package files have \\"local\\" links to each other that need to be resolved?",
- "Is there reason why package files need to be parsed together (in serial) instead of independently?",
- "What format/syntax is the package file in? e.g. JSON, TOML, custom?",
- "How do you suggest parsing the file? Using an off-the-shelf parser, using regex, or can it be custom-parsed line by line?",
- "Does the package file structure distinguish between different \\"types\\" of dependencies? e.g. production dependencies, dev dependencies, etc?",
- "List all the sources/syntaxes of dependencies that can be extracted:",
- "Describe which types of dependencies above are supported and which will be implemented in future:",
- "What versioning scheme do the package files use?",
- "Does this versioning scheme support range constraints, e.g. \`^1.0.0\` or \`1.x\`?",
- "Is this package manager used for applications, libraries, or both? If both, is there a way to tell which is which?",
- "If ranges are supported, are there any cases when Renovate should pin ranges to exact versions if rangeStrategy=auto?",
- "Is a new datasource required? Provide details",
- "Will users need the capability to specify a custom host/registry to look up? Can it be found within the package files, or within other files inside the repository, or would it require Renovate configuration?",
- "Do the package files contain any \\"constraints\\" on the parent language (e.g. supports only v3.x of Python) or platform (Linux, Windows, etc) that should be used in the lookup procedure?",
- "Will users need the ability to configure language or other constraints using Renovate config?",
- "Are lock files or checksum files used? Mandatory?",
- "If so, what tool and exact commands should be used if updating 1 or more package versions in a dependency file?",
- "If applicable, describe how the tool maintains a cache and if it can be controlled via CLI or env? Do you recommend the cache be kept or disabled/ignored?",
- "If applicable, what command should be used to generate a lock file from scratch if you already have a package file? This will be used for \\"lock file maintenance\\".",
- "Is there anything else to know about this package manager?",
-]
-`;
-
-exports[`manager readmes has same questions for all managers 3`] = `
-Array [
- "Name of package manager",
- "What language does this support?",
- "Does that language have other (competing?) package managers?",
- "What type of package files and names does it use?",
- "What [fileMatch](https://renovatebot.com/docs/configuration-options/#filematch) pattern(s) should be used?",
- "Is it likely that many users would need to extend this pattern for custom file names?",
- "Is the fileMatch pattern likely to get many \\"false hits\\" for files that have nothing to do with package management?",
- "Can package files have \\"local\\" links to each other that need to be resolved?",
- "Is there reason why package files need to be parsed together (in serial) instead of independently?",
- "What format/syntax is the package file in? e.g. JSON, TOML, custom?",
- "How do you suggest parsing the file? Using an off-the-shelf parser, using regex, or can it be custom-parsed line by line?",
- "Does the package file structure distinguish between different \\"types\\" of dependencies? e.g. production dependencies, dev dependencies, etc?",
- "List all the sources/syntaxes of dependencies that can be extracted:",
- "Describe which types of dependencies above are supported and which will be implemented in future:",
- "What versioning scheme do the package files use?",
- "Does this versioning scheme support range constraints, e.g. \`^1.0.0\` or \`1.x\`?",
- "Is this package manager used for applications, libraries, or both? If both, is there a way to tell which is which?",
- "If ranges are supported, are there any cases when Renovate should pin ranges to exact versions if rangeStrategy=auto?",
- "Is a new datasource required? Provide details",
- "Will users need the capability to specify a custom host/registry to look up? Can it be found within the package files, or within other files inside the repository, or would it require Renovate configuration?",
- "Do the package files contain any \\"constraints\\" on the parent language (e.g. supports only v3.x of Python) or platform (Linux, Windows, etc) that should be used in the lookup procedure?",
- "Will users need the ability to configure language or other constraints using Renovate config?",
- "Are lock files or checksum files used? Mandatory?",
- "If so, what tool and exact commands should be used if updating 1 or more package versions in a dependency file?",
- "If applicable, describe how the tool maintains a cache and if it can be controlled via CLI or env? Do you recommend the cache be kept or disabled/ignored?",
- "If applicable, what command should be used to generate a lock file from scratch if you already have a package file? This will be used for \\"lock file maintenance\\".",
- "Is there anything else to know about this package manager?",
-]
-`;
-
-exports[`manager readmes has same questions for all managers 4`] = `
-Array [
- "Name of package manager",
- "What language does this support?",
- "Does that language have other (competing?) package managers?",
- "What type of package files and names does it use?",
- "What [fileMatch](https://renovatebot.com/docs/configuration-options/#filematch) pattern(s) should be used?",
- "Is it likely that many users would need to extend this pattern for custom file names?",
- "Is the fileMatch pattern likely to get many \\"false hits\\" for files that have nothing to do with package management?",
- "Can package files have \\"local\\" links to each other that need to be resolved?",
- "Is there reason why package files need to be parsed together (in serial) instead of independently?",
- "What format/syntax is the package file in? e.g. JSON, TOML, custom?",
- "How do you suggest parsing the file? Using an off-the-shelf parser, using regex, or can it be custom-parsed line by line?",
- "Does the package file structure distinguish between different \\"types\\" of dependencies? e.g. production dependencies, dev dependencies, etc?",
- "List all the sources/syntaxes of dependencies that can be extracted:",
- "Describe which types of dependencies above are supported and which will be implemented in future:",
- "What versioning scheme do the package files use?",
- "Does this versioning scheme support range constraints, e.g. \`^1.0.0\` or \`1.x\`?",
- "Is this package manager used for applications, libraries, or both? If both, is there a way to tell which is which?",
- "If ranges are supported, are there any cases when Renovate should pin ranges to exact versions if rangeStrategy=auto?",
- "Is a new datasource required? Provide details",
- "Will users need the capability to specify a custom host/registry to look up? Can it be found within the package files, or within other files inside the repository, or would it require Renovate configuration?",
- "Do the package files contain any \\"constraints\\" on the parent language (e.g. supports only v3.x of Python) or platform (Linux, Windows, etc) that should be used in the lookup procedure?",
- "Will users need the ability to configure language or other constraints using Renovate config?",
- "Are lock files or checksum files used? Mandatory?",
- "If so, what tool and exact commands should be used if updating 1 or more package versions in a dependency file?",
- "If applicable, describe how the tool maintains a cache and if it can be controlled via CLI or env? Do you recommend the cache be kept or disabled/ignored?",
- "If applicable, what command should be used to generate a lock file from scratch if you already have a package file? This will be used for \\"lock file maintenance\\".",
- "Is there anything else to know about this package manager?",
-]
-`;
-
-exports[`manager readmes has same questions for all managers 5`] = `
-Array [
- "Name of package manager",
- "What language does this support?",
- "Does that language have other (competing?) package managers?",
- "What type of package files and names does it use?",
- "What [fileMatch](https://renovatebot.com/docs/configuration-options/#filematch) pattern(s) should be used?",
- "Is it likely that many users would need to extend this pattern for custom file names?",
- "Is the fileMatch pattern likely to get many \\"false hits\\" for files that have nothing to do with package management?",
- "Can package files have \\"local\\" links to each other that need to be resolved?",
- "Is there reason why package files need to be parsed together (in serial) instead of independently?",
- "What format/syntax is the package file in? e.g. JSON, TOML, custom?",
- "How do you suggest parsing the file? Using an off-the-shelf parser, using regex, or can it be custom-parsed line by line?",
- "Does the package file structure distinguish between different \\"types\\" of dependencies? e.g. production dependencies, dev dependencies, etc?",
- "List all the sources/syntaxes of dependencies that can be extracted:",
- "Describe which types of dependencies above are supported and which will be implemented in future:",
- "What versioning scheme do the package files use?",
- "Does this versioning scheme support range constraints, e.g. \`^1.0.0\` or \`1.x\`?",
- "Is this package manager used for applications, libraries, or both? If both, is there a way to tell which is which?",
- "If ranges are supported, are there any cases when Renovate should pin ranges to exact versions if rangeStrategy=auto?",
- "Is a new datasource required? Provide details",
- "Will users need the capability to specify a custom host/registry to look up? Can it be found within the package files, or within other files inside the repository, or would it require Renovate configuration?",
- "Do the package files contain any \\"constraints\\" on the parent language (e.g. supports only v3.x of Python) or platform (Linux, Windows, etc) that should be used in the lookup procedure?",
- "Will users need the ability to configure language or other constraints using Renovate config?",
- "Are lock files or checksum files used? Mandatory?",
- "If so, what tool and exact commands should be used if updating 1 or more package versions in a dependency file?",
- "If applicable, describe how the tool maintains a cache and if it can be controlled via CLI or env? Do you recommend the cache be kept or disabled/ignored?",
- "If applicable, what command should be used to generate a lock file from scratch if you already have a package file? This will be used for \\"lock file maintenance\\".",
- "Is there anything else to know about this package manager?",
-]
-`;
diff --git a/test/manager/manager-docs.spec.js b/test/manager/manager-docs.spec.js
index a5980d36ce867ba6db577170ddc30f38717ceb45..6f20bc6c5490daf5bcaa83c4f7164cf5546da970 100644
--- a/test/manager/manager-docs.spec.js
+++ b/test/manager/manager-docs.spec.js
@@ -5,7 +5,6 @@ describe('manager readmes', () => {
const managers = (await fs.readdir('lib/manager')).filter(
item => !item.includes('.')
);
- expect(managers).toMatchSnapshot();
let expectedHeaders;
for (const manager of managers) {
let readme;
@@ -22,7 +21,6 @@ describe('manager readmes', () => {
.match(/\n#### (.*?)\n/g)
.map(match => match.substring(6, match.length - 1));
expectedHeaders = expectedHeaders || headers;
- expect(headers).toMatchSnapshot();
expect(headers).toEqual(expectedHeaders);
}
}