You are not logged in.
Talking about bl-exit: https://forums.bunsenlabs.org/viewtopic.php?id=1636
I guess you really could have used some more help with testing at an earlier stage. Maybe we need a dedicated thread to call for volunteer testers from the community for times like this?
Rethinking that a bit, a single thread would soon get messy. I'm now thinking individual "Request For Testing" threads might be good, so they can be tagged [DONE]?
It might be a good way for less experienced users to contribute to BL development. After all, that's exactly the kind of feedback developers want at the final stages of a project.
If developers post clear instructions how to test their script/package/whatever, and if there are any particular things they'd like looking at, it might work.
Opinions?
Also, if done, best posted here in "development" or in "bug reports"?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I would put them in Development with a standard header such as
RFT: SOME PROGRAM
CRITERIA: Some text explaining why a test is needed, along with possible success or failure conditions, if applicable.
Then possibly in a reply I might put:
SETUP: How I set the test environment up.
TEST: The actual tests that I performed. WHAT was the input, if applicable?
RESULT: The result of the test, and in the case of failure any error messages that might apply and/or a detailed description of the failure.
I feel like standardizing the process may help developers find what they need. Also, I am thinking we could then setup a text template with all the appropriate bbcode for a template that we can copy/paste into the forum reply box. We could even go so far as to link it into the menu with a geany command.
I am just brainstorming a little here but this ought to give a nice standard way to do testing and/or bug reports.
Last edited by tknomanzr (2016-08-22 03:22:26)
Offline
Thanks @tk that sounds just right. Except, I would be inclined to ask the OP to specify the setup and tests (s)he wants performing, ie:
RFT: SOME PROGRAM
CRITERIA: Some text explaining why a test is needed.
SETUP: How to set the test environment up.
TEST: The actual tests that I would like performed.
Then in a reply:
RESULT: The result of the test, and in the case of failure any error messages that might apply and/or a detailed description of the failure.
Since we are hoping to get input from relatively inexperienced users, I think we should make it as easy as possible.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Sounds reasonable to me.
Offline
^ second the signature!
###back to topic
I am an relatively inexperienced user and think this is a great idea!
*split the threads
*create the templates
*let the dev decide whether or not to limit the tests by defining a special setup
When it comes to fieldtesting I would want to have people to behave in a way they are used to, in order to see limitations or problems I probably wouldn`t even have thought of.
naik --greetz
Last edited by Naik (2016-08-25 20:22:58)
"Kaum macht [Mensch]* es richtig, funktioniert es sofort!"
BL-Kitchen Codeberg
Offline
When it comes to fieldtesting I would want to have people to behave in a way they are used to, in order to see limitations or problems I probably wouldn`t even have thought of.
Exactly!
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
If I may make a suggestion:
Index » Development & Suggestions » Request For Testing » RFT: bl-aerosnap by Unia
Index » Development & Suggestions » Request For Testing » RFT: notify-broadcast by johnraff
A new sub-fora: » Request for Testing - keeps them all together and easier to see find in the future.
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
^ As I understand FluxBB mechanics, we don't have the flexibility to add a sub-subforum within a subforum. I'm sure a separate Request For Testing subforum under Distro Development would be equally unambiguous.
Be excellent to each other, and...party on, dudes!
BunsenLabs Forum Rules
Tending and defending the Flame since 2009
Offline
I guess whoever is working/contributing to an RFT thread knows where it is, and it will always be near the top while active. And in the future it won't really matter.
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Speaking of which.. Is there a need / argument for an "archived" section here? For sort of historically important, and safe from deletion but not necessarily needed to be stickied, which keeps the threads at the top of the forum.
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
@ damo
My thinking was that if they were in their own place, they'd be easier to see and in the future - new users logging in would see the "history" of how forum members can help by testing. Or any of the Guests online: 31 - would see them all bunched together.
Just a thought....
@pvsage - yes, my wording was off ... "a separate Request For Testing subforum under Distro Development" is what I meant.
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline