Diagnostics

What is a diagnostic?

Diagnostics are meant as a tool for both consultants and developers to evaluate how they are doing in the course. They are a chance to receive judgement-free feedback so that developers can identify bad habits and know what they need to study in order to be successful in WDI.

When should I submit a diagnostic?

You must submit a diagnostic within the time specified - usually a 1/2 hour after the diagnostic was given. Late diagnostics will not be evaluated unless you have an IEP which allows you to submit diagnostics later.

When will I get feedback?

You should receive feedback within a week of when the diagnostic was submitted. Sometimes the feedback will ask you to checkout the solution branch of the diagnostic, so you can see the answers to questions you missed.

How do I submit diagnostics?

Before working on the diagnostic...

1. Change into your WDI directory.
2. Fork and clone the diagnostic repository.
3. Change into the new directory.
4. Create and checkout a branch named response.

```sh
git branch response
git checkout response

# OR

git checkout -b response
```

While working on the diagnostic...

1. Follow any further instructions in the diagnostic README.
2. Make small, cohesive commits with a good commit message.

After working on the diagnostic, before time runs out...

1. Push your changes to your fork.

```sh
git push -u origin
```

1. Issue a pull request from your response branch to the upstream master branch.