Giter Club home page Giter Club logo

guts's Introduction

Guts-DotNetEssentials

In this repository you can find (Visual Studio) starter solutions for the exercises of the .NET Essentials course of PXL-Digital.

alt text

The exercises are grouped by chapter. There is a (Visual Studio) solution for each chapter. A chapter solution contains multiple projects:

  • A WPF project for each exercise. E.g. Exercise01
  • A test project for each WPF project. E.g. Exercise01.Tests

alt text

The WPF projects are (mostly) empty and waiting for you to complete them. The matching test projects contain automated tests that can be run to check if your solution is correct.

Getting Started

First you need to clone the files in this repository on your local machine. You will use the Visual Studio git capabilities to accomplish this.

Clone the repository

Start Visual Studio and select "Clone or check out code".

  • Click on the Clone or Download button in the upper right corner of this webpage
  • Copy the url of this repository

alt text

  • Paste the url you copied earlier into the field "Repository Location"
  • Choose a local path, this is a local folder where the files will be copied to
  • Click on the Clone button

alt text

Now you have a local copy of the online repository in which you can complete your exercises.

alt text

Double click the solution that contains the chapter exercises you want to work on. Alternatively, you can just double click a solution file (.sln) from an explorer window to start up Visual Studio with the solution opened up.

Register on guts-web.pxl.be

To be able to send your tests results to the Guts servers you need to register via guts-web.pxl.be. After registration you will have the credentials you need to succesfully run automated tests for an exercise.

Start working on an exercise

Let's assume you want to make exercise 5 of chapter 5.

  1. Open the solution in the folder "Chapter 5". You can do this by doubleclicking on the .sln file from an explorer window or by opening visual studio, clicking on File → Open a project or solution and selecting the .sln file.

  2. Build the solution (Menu: Build → Build Solution or Ctrl+Shift+B)

  3. Locate the project "Exercise 5" and set it as your startup project

alt text

  1. Write the code you need to write

Run the automated tests

Let's assume you are working on exercise 5 of chapter 5.

  1. Open the Test Explorer window (Menu: Test → Test Explorer)
  2. In the top right corner, click on the group by button and make sure the automated tests are grouped by project (see the picture below). If you don't see any tests appearing, you probably should (re)build your solution.

alt text

  1. Right click on the project that matches your exercise and click on Run to execute the tests.
  2. The first time you run a test a browser window will appear asking you to log in. You should fill in your credentials from guts-web.pxl.be.

alt text

FAQ

Why won't my tests run?

The first time it can happen that you see the tests in the Test Explorer but if you run the tests, nothing happens. Try to clean your solution (Build → Clean Solution) and then to rebuild your solution (Build → Rebuild solution).

Why can't I see my test results on the Guts website? Locally all my tests are green.

After the tests are run, the testrunner will try to send your results to the server. In the Output Window you can see a log of the steps that are taken. If anything goes wrong, you should be able to find more info in the Output Window.

The test results will only be sent to the server when you run all te tests of an exercise at once. If you run the tests one by one the results will not be sent to the servers.

Inspect the test results

Tests that pass will be green. Tests that don't pass will be red.

The name of the test gives an indication of what is tested in the automated test. If you click on a test you can also read more detailed messages that may help you to find out what is going wrong.

alt text

Although it is not a guarantee, having all tests green is a good indication that you completed the exercise correctly.

Check your results online

Test results of all students are sent to the Guts servers. You can check your progress and compare with the averages of other students via guts-web.pxl.be. Login, go to ".NET Essentials" in the navigation bar and select the chapter you want to view.

alt text

Save (commit) your work

It could happen that the code in the online repository changes and that you need to pull (download) a new version of the start code in your local repository. The online repository does not contain your solutions. Pulling a new version of the code could result in you losing your work.

To avoid this you should regularly commit (save) your work in your local git database. If you have commited your work an you pull a new version, git will be able to automatically merge your work with the online changes. It is recommended to do a git commit every time you complete an exercise.

  • Go to Git Changes

alt text

  • In the Git Changes screen you get an overview of the changes you made locally. Fill in a commit message (describing what you did) and click on the Commit All button. Your changes are now saved in your local git database.

alt text

  • By clicking on the Solution Explorer tab you go back to the main view for this local repository

Get a new version of the start code

It could happen that the lecturers fix bugs in the automated tests of the startcode or add new exercises and/or tests. Follow the steps below to get the new version of the code:

  • Commit your work locally (see previous section)
  • Go to Git Changes
  • In the upper right corner, click the three dots ...
  • Select Pull from → origin. This will merge your saved commit with the online commit in your local repository.

guts's People

Contributors

wesleyhendrikx avatar krishermans avatar hursittarcan avatar ingridvanherwegen avatar

Stargazers

Hursit Tarcan avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.