Bug hunters topic

[Aswan jaguar]

Finally,I have finished the ones that I took to check -[fixed] & more - from archive reports forum.More than 80 bugs checked 65 of them were fixed for good [fixed/closed] and around 15+ were still bugged and needed to be worked again.

I move on to the next 50 reports which has already some checked by BAgate.So I am taking the 10th page as it stands now between Esper Charm and Weapon Surge which I have marked with

[stassy]

OI3.dck done, now onto OoA series

[Aswan jaguar]

@BAgate please check your pm and respond please.

[gmzombie]

so now that we have had an update can we get a folder that is within the fixed folder to separate fixes we cant check yet and the ones we are able to. or a date for exact so we can start to check out these fixes. on a side note i noticed whenever i try to debug a card in lately it will freeze the game and crash.

[stassy]

It should be available once the new moderators are up, waiting for the last pending moderator and we roll out.

Do you crash when you debug a card in hand or directly in play? If your card is not a permanent or a permanent with ETB effect it will 100% crash after resolve, you need to put 1st into hand, then cast it normally (or use the mana generator in debug mode)

[Aswan jaguar]

so now that we have had an update can we get a folder that is within the fixed folder to separate fixes we cant check yet and the ones we are able to. or a date for exact so we can start to check out these fixes. on a side note i noticed whenever i try to debug a card in lately it will freeze the game and crash.

All the new reports the ones after the update has been released go on the first page always and go to page 2 and so on.... as bugs are reported and archived.These bugs are not to be checked until a v2 or a completely new update is up.
I don't know if we can tag them easily as a group with colour or some other way so we have:
1- to be checked under Next update.
2- check Now

Or have a subfolder in archived reports where all new bug reports that have been worked,checked,unconfirmed,etc and have to be archived after a new update has been released go there and are left alone until the next update and then they all are moved to the main archived forum to be tested and leave their place to be taken from new worked,fixed reports.

[stassy]

I like the idea of pending fixed bugs from a v1 release, we however need to be sure that there will be a v2, meaning if no major bug is found, there won't be any v2 and the check will only happen next patch.

Also my biggest concern is that something that was fixed several patch ago get broke, like the crash on cancel for flashback or worse a specific card issue : we can't definitely tag something "definitely fixed" because we don't really know what the next patch will break...and as the list of fixed card get tremendous, it's unlikely that we will have the courage for a 3rd or 4rth check on the whole list (personally I won't )

[BAgate]

Considering the number of recurrences, wouldn't it be better to just mark a bug as fixed, retire it, and then re-report it if it pops up again? I think it would be easier for everyone (I know I sometimes get confused by all the many layers of report/confirmed/fixed/broken again/fixed again/etc...), especially considering the 300 places old bug reports can be (which will get worse if the proposed new folder structure is adopted).

[stassy]

That was the original idea of the Archived section, however another folder could help by avoiding unnecessary check (though it would be easy to avoid a just-fixed-report check by looking at the OP date.

Or make a web 2.0 style section, each moderator choose and move the threads to a section they own, check them and move then back to archived if non bugged and to bug section if bugged, but maybe it's going a bit far...

[gmzombie]

i also like the idea of having a current buglist folder and a pevious buglist folder. while it might seem a bit confusing it will allow us to know which ones can be tested and not. the last month there has been a bunch of bugs that have been confirmed and fixed and it would be nice to know when everything started. if we do go on longer than a month then an update there is at least a marker that says these have been confirmed and these are from the new update. sure there will be some things that get broken and that is why we test. it will happen but its no big deal.

[Korath]

and as the list of fixed card get tremendous, it's unlikely that we will have the courage for a 3rd or 4rth check on the whole list (personally I won't )

The usual armor against regressions is an automated test suite. We don't know either the topmost layer (the user interface) or bottommost layer (what really happens when a trigger is run or a card is destroyed) of Manalink well enough to make that practical.

Keeping track of whether a bug is reported, confirmed, fixed, released, regressed, or just forgotten about is hard!

Well, that's one of the things a bugtracker is designed to do. Best we can do with forum software is put that information in the thread title, and make just one or two divisions of them (currently, either "reported/confirmed/regressed" or "fixed/released/forgotten") viewable by dividing into subfora.

[BAgate]

I like stassy's idea. My ideal setup would be to replace the archive folder with a 'fixed bugs' folder which contains a 'retired' folder (which replaces the [fixed] bug archive) and a folder for each mod. As bugs are reported fixed they are moved to the 'fixed bugs' folder. After each update (patch or v2) the mods check the fixed bugs by moving them into their folder and then either returning them to the bug reports folder if they are still bugged or moving them to the 'retired' folder if they are fixed. That way the developers just have to look in the bug reports folder, the mods don't duplicate effort in checking fixed bugs, the 'retired' folder persists as an archive of previous bugs if we need a reference, and everything is in one file structure, without having to look in multiple file trees to find things..

[stassy]

Yes, the intend of the Archived folder was originally to ease the task for developers, though it failed because non confirmed/non fixed reports are still dumped there if they are staying for too long in the Bug Reports root section, thus forcing them to look into it too.

As Korath said, due to the forum structure it's quite hard to create a bugtrack section with personalized section, though I asked Huggy to create another subfolder called Pending Reports.

If the need for personalized section arise, I will try to ask for more subsections, though I don't think we need that much because some issues like Moderator leaving or joining could be a headache to manage (or tag section with Anynomous Moderator X with X an assigned number for each mod...holy cow, we are modding the forum now ).

[stassy]

Ok 2nd section is up, I am starting to move all fixed bugs from PTT there until v2 or next patch (and until all mods are approved so they can move them too), let's see how it goes before going further in forum customization

Edit: Updated moderators rules

[gmzombie]

ok so what is everybody working on right now. i can take some to do.