Lucas Bajolet 31b6109430 packer_test: hide run and introduce Output ... When using a PackerCommand, the Run function was made public as a way to access the contents of an execution. This was clumsy as it had too many responsabilities, and was not needed strictly as Assert was performing the executions, as many times as required. This could introduce cases in which one run as spent by the caller, then the remainder were executed through Assert. Therefore, we change this convention. Now, run is private to the type, and only through Assert can a command be executed. If a test needs access to a command's output, stderr, or error, it can do so through the Output function, which requires Assert to be called first.		2024-09-11 16:08:51 -04:00
..
templates	packer_test: make packer test suite modular	2024-08-13 14:52:43 -04:00
init_test.go	packer_test: add func to change assert behaviour	2024-09-11 16:08:51 -04:00
install_test.go	packer_test: rename/split lib into common/check	2024-09-11 16:08:51 -04:00
loading_test.go	packer_test: rename/split lib into common/check	2024-09-11 16:08:51 -04:00
plugins_remove_test.go	packer_test: hide run and introduce Output	2024-09-11 16:08:51 -04:00
sample_config.json	packer_test: make packer test suite modular	2024-08-13 14:52:43 -04:00
suite_test.go	packer_test: rename/split lib into common/check	2024-09-11 16:08:51 -04:00