Create TestCalcJoinSingleAssetTokensIn test case to fall outside of the error tolerance

[p0mvn]

I'm confused as to why expectShares is double what is in the previous test when the total liquidity isn't being doubled

The logic was the following - here we are adding 2 tokens in that have equal weights and amounts in, so the liquidity would double. In the previous case, there was only one token in.

However, it seems that these should still not be equal because after the first join we would have more shares created for one of the tokens, right? As a result, the second join would have fewer shares returned than the first one. Seems that this test is passing because of the error tolerance

This is interesting – I wonder if we can set up a case where this falls outside of error tolerance just for proper coverage? Or would it always pass due to error tolerance?

Originally posted by @AlpinYukseloglu in #1721 (comment)

[p0mvn]

We need a test case to fall outside of the error tolerance for when we are testing multi token calcs by joining one after another in calcJoinSingleAssetTokensIn.

We should be able to achieve that by having large token in values relative to the pool liquidity

[stackman27]

Hi @p0mvn can i give this a shot?

[p0mvn]

Hey @stackman27 . Yes, please, that would be awesome