Using a Bitcoin-Qt v0.16.0 ([downloaded from bitcoin page](https://bitcoin.org/bin/bitcoin-core-0.16.0/bitcoin-0.16.0-osx.dmg)) in an macOS High Sierra 10.13.4 

When I start after a fresh install Bitcoin-Qt as a mainnet node and wallet, the wallet prompt that about 203gb is going to be used in my disk
![image](https://user-images.githubusercontent.com/20187136/39899688-ba820bfe-5493-11e8-87d9-460ed5716a02.png)

When I start the node and wallet as testnet, shows the same message about the 203gb disk usage
![image](https://user-images.githubusercontent.com/20187136/39899756-17b31214-5494-11e8-8a57-60e604e74afb.png)

It seems that the second time the message is wrong, due that the testnet database uses about 14gb.
public:
    CTestNetParams() {
        strNetworkID = "test";
        consensus.nSubsidyHalvingInterval = 210000;
        consensus.BIP16Exception = uint256S("0x00000000dd30457c001f4095d208cc1296b0eed002427aa599874af7a432b105");
        consensus.BIP34Height = 21111;
        consensus.BIP34Hash = uint256S("0x0000000023b3a96d3484e5abb3755c413e7d41500f8e2a5c3f0dd01299cd8ef8");
        consensus.BIP65Height = 581885; 
        consensus.BIP66Height = 330776; 
        consensus.powLimit = uint256S("00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff");
        consensus.nPowTargetTimespan = 14 * 24 * 60 * 60; 
        consensus.nPowTargetSpacing = 10 * 60;
        consensus.fPowAllowMinDifficultyBlocks = true;
        consensus.fPowNoRetargeting = false;
        consensus.nRuleChangeActivationThreshold = 1512; 
        consensus.nMinerConfirmationWindow = 2016; 
        consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].bit = 28;
        consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nStartTime = 1199145601; 
        consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nTimeout = 1230767999; 
        
        consensus.vDeployments[Consensus::DEPLOYMENT_CSV].bit = 0;
        consensus.vDeployments[Consensus::DEPLOYMENT_CSV].nStartTime = 1456790400; 
        consensus.vDeployments[Consensus::DEPLOYMENT_CSV].nTimeout = 1493596800; 
        
        consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].bit = 1;