Bitwarden-app-android-iphon.../test/Common/AutoFixture/Attributes/AutoSubDataAttribute.cs

using AutoFixture.AutoNSubstitute;

namespace Bit.Test.Common.AutoFixture.Attributes
{
    public class AutoSubstitutionData : CustomAutoDataAttribute
    {
        public AutoSubstitutionData() : base(typeof(AutoNSubstituteCustomization))
        { }
    }
}
Port send jslib to mobile (#1219) * Expand Hkdf crypto functions * Add tests for hkdf crypto functions Took the testing infrastructure from bitwarden/server * Move Hkdf to cryptoFunctionService * Port changes from bitwarden/jslib#192 * Port changes from bitwarden/jslib#205 * Make Send Expiration Optional implement changes from bitwarden/jslib#242 * Bug fixes found by testing * Test helpers * Test conversion between model types * Test SendService These are mostly happy-path tests to ensure a reasonably correct implementation * Add run tests step to GitHub Actions * Test send decryption * Test Request generation from Send * Constructor dependencies on separate lines * Remove unused testing infrastructure * Rename to match class name * Move fat arrows to previous lines * Handle exceptions in App layer * PR review cleanups * Throw when attempting to save an unkown Send Type I think it's best to only throw on unknown send types here. I don't think we want to throw whenever we encounter one since that would do bad things like lock up Sync if clients get out of date relative to servers. Instead, keep the client from ruining saved data by complaining last minute that it doesn't know what it's doing. 2021-01-25 21:27:38 +01:00			`using AutoFixture.AutoNSubstitute;`

			`namespace Bit.Test.Common.AutoFixture.Attributes`
			`{`
			`public class AutoSubstitutionData : CustomAutoDataAttribute`
			`{`
			`public AutoSubstitutionData() : base(typeof(AutoNSubstituteCustomization))`
			`{ }`
			`}`
			`}`