BRFennPocock: /* Reporting Failures */

2016-10-26T18:00:15Z

‎Reporting Failures

BRFennPocock: Created page with "== What Needs Testing == Check Builder:Status first You can validate anything on that checklist again Check also Core:News or Builder:News for things that are n..."

2016-07-22T19:33:29Z

Created page with "== What Needs Testing == Check Builder:Status first You can validate anything on that checklist again Check also Core:News or Builder:News for things that are n..."

New page

== What Needs Testing ==

Check [[Builder:Status]] first

You can validate anything on that checklist again

Check also [[Core:News]] or [[Builder:News]] for things that are new and may need testing

== Reporting success ==

If a service is marked “GO” and it's working, that's great. No action needed.

If a service is marked “GO” and it ''fails'' — report it (below)!

If a service is marked “NO GO” and it fails, that's expected, sadly. No action needed.

If a service is marked “NO GO” and it's working,

* Send a quick [[WALLOPS]] that it's back — like <tt>#(wallops "The gossipnet netsplit is cured")</tt>
* Edit the status page and change “<nowiki>''NO GO''</nowiki>” to “GO”
* If there's a BUG link, remove it.
* In the ''Summary:'' box under your edit, put something about how you verified that it was working

The Summary will show up on the History of the page, so we can figure out what's happening.

== Reporting Failures ==

If something that was GO turns to a ''NO GO'':

* Send a [[WALLOPS]] to see if anyone expected it to be acting differently.
** Sometimes we Builders are lame and can fix a simple mistake really fast without doing much else.
* If there isn't an '''immediate''' reply, Edit the status page
** Turn <tt>GO</tt> into <tt><nowiki>''NO GO'' ~~~~</nowiki></tt> which will “sign” it with your name
** If you have more information, write a BUG link with your handle and the date and time instead: eg, <tt><nowiki>''NO GO'' [[BUG catvlle 20160722 3pm]]</nowiki></tt> or something.
** Save the page; the BUG link will be red; click it, and then click the bold red text again to create the page.
** Describe what you did to recreate the bug
** It can help to issue <tt>#(debug-info)</tt> and cut-and-paste the whole block onto the wiki page.

@@ Line 32: / Line 32: @@
 ** Sometimes we Builders are lame and can fix a simple mistake really fast without doing much else.
 * If there isn't an '''immediate''' reply, Edit the status page
-** Turn <tt>GO</tt> into <tt><nowiki>''NO GO'' ~~~~</nowiki></tt> which will “sign” it with your name
+** Go to https://github.com/romance-ii/violet-volts/issues and post a new Issue. Give it a brief title and add comments with details.
 ** It can help to issue <tt>#(debug-info)</tt> and cut-and-paste the whole block onto the wiki page.

Testing - Revision history

BRFennPocock: /* Reporting Failures */

BRFennPocock: Created page with "== What Needs Testing == Check Builder:Status first You can validate anything on that checklist again Check also Core:News or Builder:News for things that are n..."