unit-testing

Is your feature request related to a problem? Please describe.

If you want to use sinon with mocha, you shouldn't forget to restore the sinon sandbox after each test. This is documented here in general setup.

Since version 7.2, mocha supports root hooks. It is a way to export mocha root hooks (beforeEach, afterEach etc) fr

Currently, when comparing strings, options like ignoreLineEndingDifferences and ignoreWhiteSpaceDifferences require there be at least one instance of the various characters

// Succeeds
Assert.Equal("    ", " ", ignoreWhiteSpaceDifferences: true);
// Fails
Assert.Equal("    ", String.Empty, ignoreWhiteSpaceDifferences: true);

... I'm looking for a way to compare two s

This PR contains the following updates:

Description

Nested AssertionScopes only report the outer-most scope reportables on failure. This is true regardless of whether the outer scope has any reportables -- i.e., if only the inner scope has reportables, nothing is reported.

Complete minimal example reproducing the issue

[TestMethod]
public void TestNestedAssertionScopes()
{
    using (var outerScope = new A

Add singular form of the following:

getErrors() -> getError()
getWarnings() -> getWarning()

The idea is to return the first error/warning of a field, instead of an array.
Unlike getErrors/getWarnings that can either take 0 or 1 arguments, getError/getWarning must receive a field name.

Function signature:

function getError(fieldName: string): string;
function getWarning(fieldNam

If you want to contribute android projects to awesome-android-kotlin-apps, Pull Requests are welcomed!

If you are a beginner looking for your first contribution to Open Source, I will help you with Pull Request and contributing guide. 🐣 contact: awesomedevnotes@gmail.com / twitter: https://twitter.com/androiddevnotes

Feel free to send Pull Requests, fix typos, grammatical mistakes ...

Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Rubberduck version [Version 2.5.2.6030
OS: Microsoft Windows NT 10.0.22000.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.14701.20226
Host Executable: WINWORD.EXE

Description
Language inspection for assignment of LCase suggests usi

I'm mocking a protocol with a function that looks like this:

func foo(
    completion: @escaping (
        _ bar: Int,
        _ baz: Int,
        _ qux: Int
    ) -> Void
)

The generated mocks do not properly remove the line breaks before attempting to put it into a single-line string literal, resulting in the errors Unterminated string literal, `Consecutive statement