We need the file reference as a "backup" for the origin datetime (we read last modified, if for whatever reason we don't find anything in the file's metadata). Hence I just re-used the file reference for reading the metadata + lastmodified, instead of using the inputstream - but it would in fact just work as well.
Well, we do have already Parametrized tests which allow us to do the same, but a bit reversed. DynamicTest API is less-known. Do we really need it? Thnx)
I think it depends on your need. If your list of parameters fits in a CSV, then ParameterizedTest is enough. But being able to provide you own tests based on arbitrary logic can be useful for test automation in more complex environments (like, if resources must be fetched across network, depends on some system spec, etc.).
Great tutorial, as always. Thank you!
Took forever to get to the topic itself. Going to find other resources on this topic.
:*(
Thank you!
Very interesting, please keep it up 👍🏻
Great Video as always!
Why can't we pass an InputStream to the MetadataReader?
We need the file reference as a "backup" for the origin datetime (we read last modified, if for whatever reason we don't find anything in the file's metadata). Hence I just re-used the file reference for reading the metadata + lastmodified, instead of using the inputstream - but it would in fact just work as well.
Well, we do have already Parametrized tests which allow us to do the same, but a bit reversed. DynamicTest API is less-known. Do we really need it? Thnx)
I'm a big believer in "whatever works, works", as in, I have no preference towards either one. Just felt like making it a dynamic test :)
I think it depends on your need. If your list of parameters fits in a CSV, then ParameterizedTest is enough. But being able to provide you own tests based on arbitrary logic can be useful for test automation in more complex environments (like, if resources must be fetched across network, depends on some system spec, etc.).
First!!! 🍻