WBSC-like Scoring Creator

REPORTING BUGS

In every computer program there is at least one bug.

This saying might be a little exaggerated, but generally it is quite hard to keep any application error prone. I am doing my best developing "WBSC-like Scoring", also having quite solid bunch of automated tests with dozens of situations to test every time before I add/update/fix something, but basically, I am sure there are still mistakes hidden around and waiting to be discovered. And if not mistakes, then you'll probably come up with some "nice to have" new features I haven't thought about yet.

I am ready for all your input. Here on this page, you can find details about the reporting process.

GitHub issues

GitHub provides a simple, yet sufficient bug/feature tracking system, which is being used for this project.

You can find all the issues related to "WBSC-like Scoring" HERE. The default filter shows opened issues, that are known to me, but are about to be dealt with yet.

If you are familiar with GitHub, feel free to open a new issue on your own. I will try to address it ASAP.

Manual reporting

If you're not sure how to deal with GitHub, you are of course welcome traditional ways of communication.

The best option is to write me an email to alois.seckar{'@'}gmail.com.

Alternative ways of contacting me via social media are listed HERE.

What to include in the report?

To be able to track down the issue I urge you to keep some basic structure of the reports with all the necessary details attached. Please always try to include following points:

What is wrong?

A brief, yet meaningful explanation of what seems to be broken/malfunctioning.

Reproduction

A sequence of user steps and interactions leading to the situation. This is important, because some things depend on the exact order of things, and I might not be able to do it the same way unless you tell me how.

Screenshots

A visualization of the problem often speaks for itself. Actually, good screenshots may be worth more than the text explanation alone.

I would be interested in the picture of the output (to see what is wrong), but also (and MAINLY) of the inputs, because the cause may often be hidden right there. Please always try to attach them.

Console output

This is an advanced topic, but it can also help me a lot. If you press F12 in most of the browsers (on desktop), you gain access to a thing called "Console". As you visit any website, the actions your browser is performing during rendering the content may manifest here. Especially when some error occurs, a red text may appear here giving hints to developers about the cause.

Here is an example of console output (after I picked wrong file type during importing input):