Skip to content

Commit 88b1d68

Browse files
authored
Merge pull request #8415 from alessandro-avila/patch-2
Update unit-test-basics.md
2 parents 08844f7 + bbbe468 commit 88b1d68

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/test/unit-test-basics.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ For an introduction to unit testing that takes you directly into coding, see one
3434

3535
- [Write unit tests for C/C++ in Visual Studio](../test/writing-unit-tests-for-c-cpp.md)
3636

37-
## The MyBank solution example
37+
## The Bank solution example
3838

3939
In this article, we use the development of a fictional application called `MyBank` as an example. You don't need the actual code to follow the explanations in this topic. Test methods are written in C# and presented by using the Microsoft Unit Testing Framework for Managed Code. However, the concepts are easily transferred to other languages and frameworks.
4040

@@ -51,7 +51,7 @@ We create a `MyBank` solution that contains two projects:
5151

5252
- `Accounts`
5353

54-
- `BankDb`
54+
- `BankDB`
5555

5656
Our first attempt at designing the `Accounts` project contains a class to hold basic information about an account, an interface that specifies the common functionality of any type of account, like depositing and withdrawing assets from the account, and a class derived from the interface that represents a checking account. We begin the Accounts projects by creating the following source files:
5757

@@ -123,7 +123,7 @@ For C#, it is often quicker to generate the unit test project and unit test stub
123123

124124
### Create the unit test project and unit tests manually
125125

126-
A unit test project usually mirrors the structure of a single code project. In the MyBank example, you add two unit test projects named `AccountsTests` and `BankDbTests` to the `MyBanks` solution. The test project names are arbitrary, but adopting a standard naming convention is a good idea.
126+
A unit test project usually mirrors the structure of a single code project. In the MyBank example, you add two unit test projects named `AccountsTests` and `BankDbTests` to the `Bank` solution. The test project names are arbitrary, but adopting a standard naming convention is a good idea.
127127

128128
**To add a unit test project to a solution:**
129129

0 commit comments

Comments
 (0)