Skip to content
#

unit-testing

Here are 3,738 public repositories matching this topic...

SwifterSwift
GerdC
GerdC commented Jul 29, 2021

Is your feature request related to a problem? Please describe.
The existing SwifterSwift extension MKPolyline.coordinates uses method getCoordinates that is defined in MKMultiPoint and not in MKPolyline.
MKPolyline extends MKMultiPoint.
The negative effect is that this extension is not available in all subclasses of MKMultiPoint where this extension makes sense, namely MKPolygon

**Descr

sinon
fatso83
fatso83 commented May 25, 2021

Is your feature request related to a problem? Please describe.
Today we silently ignore stubbing issues, such as trying to use sinon.stub(obj, 'prop'), when obj.prop is a synthetic getter. From a user perspective, it is probably more user friendly to be explicitly told immediately that this Object.descriptor is non-configurable (perhaps even with a link to a Sinon doc page!) and cannot be

augustoproiete
augustoproiete commented Nov 21, 2020

Currently when calling the MSBuild alias with an MSBuildSettings, we need to set the target using the WithTarget extension method.

MSBuild("./my-app.sln", new MSBuildSettings
{
    Configuration = "Release",
    ToolVersion = MSBuildToolVersion.VS2019,
}.WithTarget("Build")); // <<<###

It would be nice if we could use a property, with a string, which would make it more na

fluentassertions
dbreese
dbreese commented Jul 14, 2021

Take this class, for example:

`
import Foundation

// some comment has import SOMEBADTHING
public protocol TestProtocol: AnyObject {
func doSomething() -> Void
}
`

The generated mock ends up having:

... import SOMEBADTHING ...

Looks like it is looking for "{import .*}" in source files and just adding that verbatim to the output file, causing compile issues.

A9G-Data-Droid
A9G-Data-Droid commented Oct 4, 2021

Justification
Release versions should not contain debugging support files.

Description
These files add 13MB of junk to the installation that shouldn't be there for normal users. The purpose of these files is to debug release builds. They shouldn't be included in the final installation.

The total install folder is 29.3MB so the PDB files make up %44 of the installation size.

![i

Improve this page

Add a description, image, and links to the unit-testing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the unit-testing topic, visit your repo's landing page and select "manage topics."

Learn more