LaunchCodeEducation / LaunchCodeEducation/csharp-web-dev-curriculum
Chapter 6 Unit Testing Example Code doesn't follow C# syntax convention
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Text code block:
namespace CarTests
{
[TestClass]
public class CarTests
{
//TODO: add emptyTest so we can configure our runtime environment
[TestMethod]
public void EmptyTest() {
Assert.AreEqual(10,10,.001);
}
// ... other TODOs omitted here
}
}
Suggested change: Format method using Allman style convention
namespace CarTests
{
[TestClass]
public class CarTests
{
//TODO: add emptyTest so we can configure our runtime environment
[TestMethod]
public void EmptyTest()
{
Assert.AreEqual(10,10,.001);
}
// ... other TODOs omitted here
}
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Chapter 6 MSTest page, at the TestClass and TestMethod section, and inspect the EmptyTest example. Done means the method opening brace follows the project's stated Allman-style C# convention without changing the example's behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100