Vinticuffs

Site Testing: Documentation, Error Reporting, and Information


Welcome to the 2019 Development server for Vinticuffs: The Classic Gaming Community.

A lot of progress has been made, and as such we are hoping to open the doors for more people to come in, visit, and make a mess of the place in the hope of fixing critical bugs and gathering feedback of the systems provided.

Sections Ready for Testing

  • Games: Addition of new profiles, Revisions are underway.
  • Articles: Addition, Editing, and Deletion of articles.
  • Forums: Addition, Editing, and Deletion of threads.

Sections Not Ready

  • Extend
  • Servers
  • Events (Technically has some functionality, but needs to be refactored with new things added to other sections before adding to ready)

Oh, there will be bugs!

Should you find an error while attempting to do something or stress testing a feature. You can utilize the following resources to either check on the status of known issues, or report new ones.

  • Discord: You can contact me (Decemberklar#0935) for #site-testing access, or DM me directly for issues found.
  • Trello: Trello is where we will post public updates of progress reports and known issues. The goal is to make a new update log every Sunday morning.
  • BitBucket: For those more tech savvy, you can add/check issues directly on our version control provider.
  • TeamWork: Team members can inform me if they would like access to this for task/detailed issue breakdowns/and more sensitive info.

When reporting issues, it's always best to give the following bits of information.

  1. What were you attempting to do?
  2. What was the expected result?
  3. What result did you receive?
  4. Location on the site you encountered the error
  5. A general time of error and/or the given stack trace (I can access stack errors personally, so a time would just let me find it quicker)

And as per usual. Never post or share sensitive information to any channel or member!

In fact - if you're coming to test the site, I heavily suggest not using a repeat password. I will end up exposing data very frequently when testing so until the site is more on the live side, I would use a brand new unique password to prevent potential breaches into other software that you may use.

Anyways, I can't express my appreciation for those coming to test this site after all these years of stagnation - and hopefully with your help we can get this sailing out the door and ready for everyone to use!

Thank you, ~ Decemberklar


Lil_Ruff 5 years ago
Ahhhhhhhhhhhhhhhhhhhhhhhhhh!

eeek. I need to test more things!