Giter Site home page Giter Site logo

christafaye / debugging-practice Goto Github PK

View Code? Open in Web Editor NEW

This project forked from jrmykolyn/debugging-practice

0.0 0.0 0.0 435 KB

A debugging exercise created for the 'Tools and Workflow for the Web' course, part of Humber College's Web Design and Development (WDDM) program.

CSS 30.02% HTML 20.27% JavaScript 49.72%

debugging-practice's Introduction

Introduction to Debugging

Introduction

This repository contains the starter files for the 'Introduction to Debugging' exercise.

As part of this exercise you will debug a simple, browser-based 'card matching' game. The HTML, CSS, and JavaScript code that makes up the game has been provided. However, it's a bit... buggy.

Rules

The game is intended to work as follows:

  • The user is presented with a selection of 3 pairs of cards, for a total of 6 cards.
  • Each pair of cards features a matching symbol.
  • All of the cards are displayed 'face down', meaning that the symbols are not visible.
  • The user will select two cards, one at a time.
  • When a card is selected it will be flipped 'face up', meaning that the symbol will be displayed.
  • If the symbols match, the cards will remain face up.
  • If the symbols do not match, the cards will be flipped face down.
  • This continues until the user has matched all 6 cards.
  • When all 6 cards have been matched, a message is displayed and the game ends.

Bonus Features

  • Users are able to change the colour of the cards by adding any one of the following values to the end of the URL:
  • #green
  • #red
  • #orange

Defects

Our users have reported the following problems:

  • I am able to select more than 2 cards.
  • Cards do not seem to be compared/matched correctly.
  • The cards are never flipped face down, regardless of whether or not they match.
  • The game does not end, even after all the cards have been matched.

Additionally, adding the #green, #red, or #orange values to the URL and then refreshing the page does not update the colour of the cards.

Approach

  • Debug and fix each defect (in order if possible). Introduce each fix as a separate commit.
  • Focus on debugging the 'rules' (part 1) before moving on to the 'bonus features' (part 2).

Please review the accompanying class materials for additional details.

Attribution

debugging-practice's People

Contributors

jrmykolyn avatar christafaye 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.