Skip to content
This repository was archived by the owner on Oct 11, 2022. It is now read-only.

Adding RFC for MapNotRunnableToFailed #71

Merged
vagisha-nidhi merged 2 commits into from
Apr 25, 2019
Merged

Adding RFC for MapNotRunnableToFailed #71

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0ced64
Adding RFC for MapNotRunnableToFailed
vagisha-nidhi Apr 25, 2019
157afa6
Adding RFC for MapNotRunnableToFailed
vagisha-nidhi Apr 25, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Adding RFC for MapNotRunnableToFailed
  • Loading branch information
@vagisha-nidhi
vagisha-nidhi committed Apr 25, 2019
commit c0ced6463913a9989f7d1bf87fb4b80681f616fa
20 changes: 20 additions & 0 deletions RFCs/010-MapNotRunnableToFailed-Attribute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# RFC 010 - Map not runnable tests to failed via runsettings

## Motivation
Some tests which have incompatible signature and cannot be executed are marked as skipped with warnings being thrown.
User should be able to configure to fail a test if it is not runnable.

### Proposed solution
Make this setting configurable via MapNotRunnableToFailed tag which is part of the adapter node in the runsettings.

Here is a sample runsettings: 
```xml
<Runsettings> 
<MSTestV2> 
<MapNotRunnableToFailed>true</MapNotRunnableToFailed>   
</MSTestV2> 
</Runsettings> 
```

### Honoring the settings 
- If no settings are provided in runsettings, default MapNotRunnableToFailed is set to false. This has been kept in regard with backward compatibility.