New bug tracker - How to Report a Bug

[delatbabel]

Hi all,

We have implemented a new bug tracking system for EiA. Unfortunately a lot of the old bugs that were around at the time Richard / Monadman was maintaining the bug list appear to have been lost. The test team has been scraping the forums to re-enter all of the bugs and re-prioritise them for the development team, but there are almost certainly some that we have missed.

Here is the location of the bug tracker:

http://eiamantis.babel.com.au/

Here is how to report bugs:

* Point your browser at http://eiamantis.babel.com.au/
* If you don't already have a login there, click on the link that says Signup for a new account. You will need to create an account by giving your email address and a login name. A link to set a password will be emailed back to you, so make sure that you use your valid email address.
* Once you have a login, and have logged in, click the "Report Issue" link at the top of the page.
* Enter as much detail as you can for your bug.
* Bugs that have saved game files attached will get higher priority and will be dealt with by the development team faster than bugs that do not have saved game files attached. Make sure you have zipped together both the .sav and the .sav.dat file for your saved game and upload it to the bug tracker along with your bug.

Other notes:

* Please stop using the "Reporting Bugs post-1.02" thread and create new bug reports in the bug tracker.
* Please stop using the main / non-technical support forum for creating bug reports.
* If you aren't sure if something is a bug or if it has been reported before, please feel free to discuss it in the technical support forum. Eventually, all bugs will have to go into the bug tracker, however, so if you're asked to enter something there please don't feel offended if you've already mentioned it here in this forum.

I apologise for having to ask everyone to do this but I'm sure that this is working towards a more robust and more bug-free EiA product for everyone.

Thanx,

[delatbabel]

... Check the attachments for the bug list.

[DCWhitworth]

Thanks for the work on this Del I'm sure it's appreciated by the community.

Could I suggest you review the format of the list you've posted here ? It's not very easy to read nor to sort. A TSV or CSV list would make searching it a little easier, although putting it into an attachment perhaps isn't very visible or accessible, for one thing it won't show up on forum searches.

Sorry I don't mean to come across as negative, I think this is a very positive move, I just want to try and provide some constructive feedback.

[delatbabel]

I did try attaching a CSV file however the forum won't let me (it only wants gif, jpg, text, or zip). I could save the CSV file as a text file however then I found my browser didn't know what to do with it.

The other options I could use are to zip the file then attach the zip file, or to save it as an openoffice spreadsheet and zip that and attach that, however that's probably getting to a level of technical that's too much for some people. At least clicking on the text file does open it in a browser window which seems easy enough for most people.

Later tonight I'll have a go at extracting the data in a different form and saving it to the forum directly, however last time I tried that it messed up the display of the post so it needs a bit more thinking and/or manual reformatting.

[delatbabel]

CSV file attached for those who are interested in it.

[delatbabel]

Note to all -- if you're not sure if some bug you have up your sleeve is already reported then mention it here. I'll have a look at the bug tracker and confirm whether it's there or not.

[pzgndr]

Three items:

Marshall said earlier "R299 should address the instability", regarding what I saw when Prussia dipped into instability and Russia lost its minors.  He also thought the issue might be Russia dipping in and out of instability incorrectly.  Should verify.

Placing a depot in an area with an enemy controlled city and not friendly unmoved corps present.  Maybe already fixed? 

UI enhancement request for better info on Unit Report screen. Show current/max factors.

[delatbabel]

ORIGINAL: pzgndr
Three items:

Marshall said earlier "R299 should address the instability", regarding what I saw when Prussia dipped into instability and Russia lost its minors. He also thought the issue might be Russia dipping in and out of instability incorrectly. Should verify.

We saw this issue mentioned on the forum but we were unable to duplicate it. Do you have a saved game where it occurs or has occurred?

Placing a depot in an area with an enemy controlled city and not friendly unmoved corps present. Maybe already fixed?

Not afaik, if you have a save game that'd be great.

UI enhancement request for better info on Unit Report screen. Show current/max factors.

I don't think that's on our list either so please elaborate and I'll put it on there.

[pzgndr]

Del, I don't have the saves but here are links to my original postings showing screenshoots for the instability and depot issues.

For the UI enhancement, here's what I suggested the other day:

Another UI request for the Unit Report screen. It would be nice if the screen was larger and/or font smaller to show both current factors and max factors for units. Normal Supply could just read Normal under the Supply column to make that one smaller.

Also, some totals for home country land unit factors would be helpful, summing total current and max factors. This would be helpful for seeing how many builds are needed. If factors in the production queue could also be shown under these totals, that would be great. For example, I could have 15/20 Cav total with 2 being built. I would then know not to build more than 3 with the current units.

Hope this helps. BTW, bug tracker list looks good. Sooner or later once everything is checked off, EiANW will shine. Looking forward to that. I'll continue to be patient and see what v1.03 brings. [8D]

[Jimmer]

ORIGINAL: DCWhitworth

Thanks for the work on this Del I'm sure it's appreciated by the community.

Could I suggest you review the format of the list you've posted here ? It's not very easy to read nor to sort. A TSV or CSV list would make searching it a little easier, although putting it into an attachment perhaps isn't very visible or accessible, for one thing it won't show up on forum searches.

Sorry I don't mean to come across as negative, I think this is a very positive move, I just want to try and provide some constructive feedback.

This format will work. Write a macro to open it using fixed widths for the column.

If nobody does so during the day today, I will write one this weekend and post it (as text). Anybody can then add it to Excel to open this text file.

Delatbabel: Can we get the file posted to an FTP server instead of (or in addition to) on the web server forums?

[delatbabel]

ORIGINAL: Jimmer

Delatbabel: Can we get the file posted to an FTP server instead of (or in addition to) on the web server forums?

Yes, it's possible, but in the next few days (I guess) the bug tracker will be open to the public. So you can log in to it yourself, create a bug report extract as a CSV file and manipulate it in Excel or OpenOffice to your heart's content.

Currently the bug database changes every hour or so at least with me and others reporting new bugs and Marshall applying new fixes. So if I put the file for download on an FTP server it'd be out of date as soon as it got there.

I'd rather spend the time that I'd otherwise spend doing that getting the bug tracker ready for public release.

[delatbabel]

ORIGINAL: pzgndr

Del, I don't have the saves but here are links to my original postings showing screenshoots for the instability and depot issues.

For the UI enhancement, here's what I suggested the other day:

Another UI request for the Unit Report screen. It would be nice if the screen was larger and/or font smaller to show both current factors and max factors for units. Normal Supply could just read Normal under the Supply column to make that one smaller.

Also, some totals for home country land unit factors would be helpful, summing total current and max factors. This would be helpful for seeing how many builds are needed. If factors in the production queue could also be shown under these totals, that would be great. For example, I could have 15/20 Cav total with 2 being built. I would then know not to build more than 3 with the current units.

Hope this helps. BTW, bug tracker list looks good. Sooner or later once everything is checked off, EiANW will shine. Looking forward to that. I'll continue to be patient and see what v1.03 brings. [8D]

OK, I have added the three issues mentioned above. Note that the first one has been there but is marked as "unable to reproduce" -- I ran a test game where I drove Prussia to instability and Russia didn't lose any minors, and so I can't repeat the issue. There are a few other issues in the bug tracker about instability and minor country control and so hopefully if there is an issue there it will be swept up with the other fixes. If, however, you see it happen again please re-report it and give us a save game.

Yes, I remember the bit about placing depots outside enemy controlled cities, I participated in that debate! I'm still not sure it's a bug as per the rules but it's in the bug tracker and Marshall said that he would fix it.

The UI request is in as well, thanks for the report.

[Jimmer]

ORIGINAL: delatbabel

ORIGINAL: Jimmer

Delatbabel: Can we get the file posted to an FTP server instead of (or in addition to) on the web server forums?

Yes, it's possible, but in the next few days (I guess) the bug tracker will be open to the public. So you can log in to it yourself, create a bug report extract as a CSV file and manipulate it in Excel or OpenOffice to your heart's content.

Currently the bug database changes every hour or so at least with me and others reporting new bugs and Marshall applying new fixes. So if I put the file for download on an FTP server it'd be out of date as soon as it got there.

I'd rather spend the time that I'd otherwise spend doing that getting the bug tracker ready for public release.

Ahhh. No need then. Thanks!

[delatbabel]

And the information you've been waiting for (copied from the edited version of the post at the top of the page).

---

Here is the location of the bug tracker:

http://eiamantis.babel.com.au/

Here is how to report bugs:

* Point your browser at http://eiamantis.babel.com.au/
* If you don't already have a login there, click on the link that says Signup for a new account. You will need to create an account by giving your email address and a login name. A link to set a password will be emailed back to you, so make sure that you use your valid email address.
* Once you have a login, and have logged in, click the "Report Issue" link at the top of the page.
* Enter as much detail as you can for your bug.
* Bugs that have saved game files attached will get higher priority and will be dealt with by the development team faster than bugs that do not have saved game files attached. Make sure you have zipped together both the .sav and the .sav.dat file for your saved game and upload it to the bug tracker along with your bug.

[delatbabel]

Thanks to everyone who has registered, logged in to, and no doubt perused the bugs and enhancement requests on the bug tracking system so far. A special prize (*) goes to Jimmer for the first community member to report a bug along with a save game that none of the test team had spotted so far.

In case you're wondering, the process from here is that:

• I or one of the other members of the test team will pick up the bug, load the save game file on 1.02k and verify that the bug exists. Also load the save game file on Marshall's latest 1.03 DEV executable in case it's been fixed there already.
• If the bug still exists, make a comment that it's been verified and assign it to Marshall. Also verify the priority and impact of the bug.
• If the bug has been fixed, mark it as resolved.
• Marshall at some stage picks up the bug, fixes it, and marks it as resolved.
• When a new pre-release EXE becomes available, one of the test team picks up the bug again and verifies that it has in fact been fixed. We are also working on a regression test programme which should in theory pick up reoccurrences of past bugs.
• Once that release goes out the door, mark the bug as "closed".

So you can see from the status of your bug report where it's at in the system, and potentially when Marshall is likely to be working on it.

(*) for suitable selected values of "special" that mean "none at all", but it was a nice thought anyway.

[Jimmer]

ORIGINAL: delatbabel

Thanks to everyone who has registered, logged in to, and no doubt perused the bugs and enhancement requests on the bug tracking system so far. A special prize (*) goes to Jimmer for the first community member to report a bug along with a save game that none of the test team had spotted so far.

...

(*) for suitable selected values of "special" that mean "none at all", but it was a nice thought anyway.

Ahhh <blushing>, gee thanks.

Whatever AM I going to do with it?

So, where did the other 103 bugs come from?

[Marshall Ellis]

Yes, I want to thank you all as well!
&nbsp;
BTW: If you don't see me fixing a lot of your bugs right away, it is because I am deep in work on AI tactical moving for my next test release!
&nbsp;
&nbsp;
&nbsp;
&nbsp;

[Jimmer]

For the leader lost one, we can semi work around it by having the other power repatriate the leader. But, he gets an extra 2PP out of the deal. So, it's not major, but not trivial either.

[bresh]

Personnaly i dont see why&nbsp;I need to go to a different site to report bugs, when its a matrixgame.
&nbsp;
Cant it be contained to matrix.games for bugs and bug reporting ?
&nbsp;
Regards
Bresh

[Marshall Ellis]

Bresh:
&nbsp;
I know Matrix is reviewing several options for this. I don't think it will happen in the next day or two but I think they intend to add this type of product on their site eventually.
&nbsp;
&nbsp;