test: avoid DNS pollution on local env

[fengmk2]

closes #3033

Checklist

• npm test passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

Description of change

[codecov]

Codecov Report

Merging #3034 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3034   +/-   ##
=======================================
  Coverage   99.75%   99.75%           
=======================================
  Files          29       29           
  Lines         829      829           
=======================================
  Hits          827      827           
  Misses          2        2

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bace243...c6b8a64. Read the comment docs.

[ghost]

@fengmk2，Your codes are technically right, however it seems it still depends on the remote server's DNS settings. Services such as 'unicom' 'telecom' will have different kinds of ways coping with the problem. Take 'unicome' as an example：

The result will be this：

So, you can ABSOLUTELY submit your codes, and I'll then make up a document to clearify this senario to cut off others' worry as well

[ghost]

It seems there's no need to use 'test-local-changed', because we can directly use 'test-local' instead.