lesson-12 TESTING QUESTIONS

[TimeKeyRoll]

In the screenshot I understand this deployer and user is coming from - hardhat-config.
But i don't understand what is a user? AND why we are mentioning them right there in the test? what is the usage?

namedAccounts: {
        deployer: {
            default: 0,
        },
        user: {
            default: 1,
        },
    },

[othaime-en]

Hey @MasterofBlockchain if you checkout the test on the repo, at the test starting from line 45. If you look at the test, the two test inside the describe deal with transfering of tokens. So we needed, to have an extra account which we can transfer tokens to and test the transfer functionality.
sidenote: I see from the screenshot you are retrieving user1 but the namedAccounts object above has user instead. Please make the necessary changes.

[TimeKeyRoll]

Oh Yaeah. Great Observation. i will change it to user1.

So user1 accounts are hardhat accounts for testing?

[othaime-en]

Yeah precisely. It is not necessarily fixed that they are reserved for testing. You could choose any account really. You could decide to use account 7 or 9 for testing. whatever works for you.

[TimeKeyRoll]

Since hardhat node gives us 19 accounts so can have any account outta them..right?

[othaime-en]

Yes. You can choose any.

[krakxn]

namedAccounts: {
        deployer: {
            default: 0,
        },
        user: {
            default: 1,
        },
    },

essentially is a set of accounts; you can arbitrarily have any set of accounts.

We use the user account, self-explanatorily, to simulate the behaviour of the user.

Note: in our script, for accounts variable we use the getter getNamedAccounts to get the set of accounts--from which we extract the deployer and user.

[TimeKeyRoll]

Perfect. So Now I understand the difference between user and a deployer.
default deployer account is 0 which is coming from metamask.
how about user account? where we are fetching it from?

[othaime-en]

The same hardhat accounts only this time, we are getting the second account (account at index 1) because the first is already assigned to the deployer

[TimeKeyRoll]

@othaime-en and @krakxn Wonderful explanation. thanks a ton.

[krakxn]

The same hardhat accounts only this time, we are getting the second account (account at index 1) because the first is already assigned to the deployer

^