Skip to content
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
Update README.md
  • Loading branch information
mbt1 authored Sep 13, 2021
commit 65c3050c7f39cf9d9917da9c2a9c0b8f3b461240
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,8 @@ The general project structure we recommend consists of one or more "code" projec

|Example Project Structure|
|-|
|![Example Project Structure](https://user-images.githubusercontent.com/298017/133068000-2d562db1-0a1f-495f-9581-31e557e37f47.png)|
|![Example Project Structure](https://user-images.githubusercontent.com/298017/133071915-2b530232-8387-44d6-a219-b7fa7f4e6832.png)
|
||

It is also recommended to change the "debug" database to a (developer-edition) SQL Server instance instead of the default localdb included with VS.
Expand All @@ -26,4 +27,4 @@ To create the test class (the schema) for tests to live in, VS is incompatible w

`CREATE SCHEMA [SomeRandomTests] AUTHORIZATION [tSQLt.TestClass];`

Following standard VS recommendations, you can then create your tests in independent files.
Following standard VS recommendations, you can then create your tests in independent files. It might be a good idea, too, to place all objects that belong to a test class in a folder under the project as show in the screenshot above.