5 Commits (packer_test_dump_commands)

Author	SHA1	Message	Date
Lucas Bajolet	7e1ddca0ec	common: add DumpCommand check to packerCommand ... In addition to dumping the results of a command, we also now dump the command itself, so we know exactly which command was invoked to produce the result we got.	1 year ago
Lucas Bajolet	cb1a4af5dd	packer_test: fix crash detection checker ... When running a black-box Packer test, crashes were to be detected automatically so that tests that crash are always reported as a failure. However, the match for detecting that Packer crashed was incorrectly formed, so those weren't detected.	1 year ago
Lucas Bajolet	11c238b9eb	packer_test: add FileGlob checker ... When trying to validate that a particular file exists after a run of Packer in a test suite, we can use the FileExists checker that we provide as part of the gadgets we added for the acceptance test suites. This approach works well, but only if we can extract a file name reliably from the output of Packer core, or if we know what to look for exactly beforehand. For other cases with a generated name however, the FileExists checker is not enough, and therefore to accomodate for those cases, we are introducing a new checker for this purpose: FileGlob. FileGlob, as its name suggests, runs a glob expression on the filesystem, and returns an error if no match was found regarding this glob expression.	1 year ago
Lucas Bajolet	44a94911da	packer_test: add FileExists checker ... Some tests will create files and directories as part of the execution path for Packer, and we need a way to check this, so this commit adds a new file gadget to do those checks after a command executes.	1 year ago
Lucas Bajolet	35b2317ef3	packer_test: rename/split lib into common/check ... The lib name for the common components for writing packer_test suites was not clear, and did not follow the convention established in Packer core and plugins. Therefore this commit does two things: first the lib is renamed into common as to follow this convention, and clearly document which components are common to all tests. Also checkers are placed in a subpackage of common, common/check, so that it is clearer what is meant to be used as checks for a command's execution status after it's been run, as part of Assert.	2 years ago