Testing

What Needs Testing[edit]

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[edit]

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 #(wallops "The gossipnet netsplit is cured")
Edit the status page and change “''NO GO''” 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[edit]

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
- 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 #(debug-info) and cut-and-paste the whole block onto the wiki page.
- https://tootsville.adventuring.click/tootstest/version can give you the Server Process info (first section) and the details of your User Agent (browser) — eg:

    The server product is tootstest, version 0.2, compiled 2016-10-24.
    
    I am running on a X86-64 machine (version Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz), 
    named Loki. Its system software is Linux, version 4.7.2-201.fc24.x86_64. My 
    Common Lisp implementation is SBCL, version 1.3.4-1.fc24.

    User-Agent/Browser: Epiphany 10.0 on Fedora 64-bit
    HTTP User-Agent header: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/603.1 (KHTML, like Gecko) Version/10.0 Safari/603.1 Epiphany/3.20.4
    Layout engine: WebKit
    Device/product: Any General Computer

- Change to GO on the checklist (if there is one) to a NO GO with a link to your new Issue. Use four tildes (~) to “sign” the NO GO. Example, if you added issue #1234: ''NO GO'' https://github.com/romance-ii/violet-volts/issues/1234 ~~~~