Fixed failing test cases around buildpacks

This commit is contained in:
nsingh@pivotal.io
2018-12-12 12:25:08 -08:00
parent 41d30ae7a9
commit eaf03960ca

View File

@@ -159,12 +159,12 @@ public class ManifestYamlEditorTest {
"- name: foo\n" +
"memory:\n"+
"- bad sequence\n" +
"buildpack:\n" +
"instances:\n" +
" bad: map\n"
);
editor.assertProblems(
"- bad sequence|Expecting a 'Memory' but found a 'Sequence'",
"bad: map|Expecting a 'Buildpack' but found a 'Map'"
"bad: map|Expecting a 'Strictly Positive Integer' but found a 'Map'"
);
}
@@ -822,7 +822,7 @@ public class ManifestYamlEditorTest {
// For now testing on the value, but if warning is instead switched to `buildpack`, this test should
// fail (expected) and updated to reflect this change
problem = editor.assertProblems(
"java_buildpack|Deprecated: Use `buildpacks` instead.")
"buildpack|Deprecated: Use `buildpacks` instead.")
.get(0);
assertEquals(DiagnosticSeverity.Warning, problem.getSeverity());
}