d-pac.docs

D-pac beta-testers guide

Welcome to the D-pac beta test.

If you don't have a Github account already create one on http://github.com

You won't be able to report bugs or other feedback without an account.

URL

http://tool.d-pac.be/assessors

Feedback

How to provide useful feedback:

Assessors

  1. Use the report issue-button on the application:

    Report issue

    Clicking the button will open the create issue page on Github:

    Create issue

    VERY IMPORTANT: automatically some relevant debugging information will be copied to your clipboard. Please paste this into the "Leave a comment"-area of the new issue:

    Paste details

    Pasting the data can be achieved by clicking in the "Leave a comment" area and subsequently pressing cmd+v [Mac] or ctrl+v [Windows].

  2. Actions description A concise, but comprehensive description of your actions leading to the bug. E.g.

    Immediately after logging in I clicked on "tutorial" in the menu.

    Make sure to provide a context when refererring to user interface elements. "I clicked the button" is rather unclear, "I clicked on 'tutorial' in the menu" describes the user element the action was taken on and also it's place in the user interface layout.

  3. Problem description A concise, but comprehensive description of what went wrong. What user interface reaction were you expecting and what reaction did you get instead?

    E.g.

    The page turned white and showed me the text "Not permitted! Your session may have expired."

    Or

    Nothing happened. I expected to see a "tutorial page", but the screen contents did not change.

  1. A screenshot Providing visual feedback is very useful, especially when it concerns scrambled layout, incorrect colours, hard-to-read text, et cetera.

    See http://www.take-a-screenshot.org/ for a clear overview on how to take a screenshot.

    You can either paste it into the "Leave comment" area, or drag-and-drop a file from Finder/Explorer to said area.

Developers

The tool logs all of its actions to the console. These output logs are really useful to me, please provide them if you encounter a bug.

Step-by-step

  1. Logging is optimized for Chrome, please use it.

  2. Immediately after opening the tool, open the console (alt+cmd+i) please type the following into the console:

     localStorage.debug = true

    Now refresh the page.

  3. You'll notice that the tool starts logging all kinds of stuff to the console. It should look something like this:

    Console log

  4. When you encounter a bug, please dump the full contents of the errors with ctrl+alt+d. (Make sure the tab of the d-pac tool has focus, not the console!)

  5. Select all text in the console and copy it with cmd+c

You can temporarily toggle the continuous time logging (e.g. the PUT http://boil.iminds.be:3020/api/timelogs/543fa94508483aba6202ac7b messages polluting the console) by typing ctrl+alt+s (again, focus should be on the webpage, not the console!) Type it again to re-enable.