Do not allow the Test ENV call Hex.pm directly

[andyduong1920]

What happened 👀

Currently, if the developer forgets to mock the external library, our test will send a real request to Hex.pm to get the latest version this brings two issues

• The unit test could fail in the future if the 3rd library has a new version on Hex.pm
• Waste 1 API call to external service

Related comment https://github.com/nimblehq/elixir-templates/pull/276/files#r1017442442

Insight 📝

Using different resources per each environment.

• Dev, Prod: Package
• Test: PackageMock

On the Test ENV, if we missed the @describetag mock_latest_package_versions: [{xx, yy}] our test won't pass.

Note

There is a workaround I'm not sure why that application environment is nil when we apply the template.

Proof Of Work 📹

1/ The test is pass 2/ Tested on my local

[andyduong1920]

@byhbt can you have a look and merge this ;) https://github.com/nimblehq/elixir-templates/pull/284