You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Readme.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,7 +194,7 @@ More examples, including parametrized model and family tests, are available in t
194
194
195
195
To avoid repeating the `TestExecutor` attribute for every test, you can [register](https://tunit.dev/docs/advanced/extension-points/#registering-a-test-executor) the executor globally using one of the following methods:
196
196
197
-
- Add the attribute to any .cs file in your project (e.g., TestsConfiguration.cs):
197
+
- Add the assembly-level attribute to any .cs file in your project (e.g., TestsConfiguration.cs):
198
198
199
199
```csharp
200
200
usingNice3point.TUnit.Revit.Executors;
@@ -203,7 +203,7 @@ To avoid repeating the `TestExecutor` attribute for every test, you can [registe
203
203
[assembly: TestExecutor<RevitThreadExecutor>]
204
204
```
205
205
206
-
-Addtheattributedirectlytoyour .csprojfile:
206
+
-Oraddtheattributedirectlytoyour .csprojfile:
207
207
208
208
```xml
209
209
<!--GlobalTestExecutorRegistration-->
@@ -217,9 +217,9 @@ To avoid repeating the `TestExecutor` attribute for every test, you can [registe
0 commit comments