[Testing] List of Bugs not commented > 1 year

[gonzoMD]

I clicked through the Bugzilla and searched for bugs that weren't commended for more than one year.
Many of them are marked of close duplicates and so they could also be allready fixed.

you may retest the bugs and post what comes out.

Here the List:

bug 147
bug 309
bug 417
bug 701
bug 905
bug 933
bug 1049
bug 1167 //Couldn't test because Inkscape crashs at StartUp
bug 1229
bug 1332 //Still present
bug 1460
bug 1560
bug 1692
bug 1693
bug 1867
bug 1868
bug 2092
bug 2132
bug 2407
bug 2468
bug 2592
bug 2623
bug 2735
bug 2743
bug 2784
bug 2821
bug 2848
bug 2952
bug 3129
bug 3138
bug 3163
bug 3262
bug 3271
bug 3313
bug 3332
bug 3380
bug 3391
bug 3430
bug 3489 //Partially fixed, should be tested further
bug 3499
bug 3546
bug 3559 //tested: doesn't work, neither with double and triple click R54610:QEMU
bug 3639
bug 3666
bug 3686
bug 3699
bug 3755 //tested: installer doesn't crash but ends with an error message after setting registry values
bug 3781
bug 3811
bug 3819 //tested: seems fixed in R54610
bug 3824
bug 3835
bug 3859
bug 3869
bug 3873
bug 3886
bug 3894
bug 3927
bug 3929
bug 3951
bug 3970
bug 3971
bug 3972
bug 3975
bug 3988
bug 3993

[FlyingIsFun1217]

What is the point of listing them all out on the forum? As you said yourself, it's not hard to do a search on old bugs.

FlyingIsFun1217

[gonzoMD]

but not everyone do it

[fred02]

What is the point of listing them all out on the forum? As you said yourself, it's not hard to do a search on old bugs.

but not everyone do it

Indeed! It also allows to coordinate the effort.

[fLuXx]

Actually, I think this is a nice idea! If I get some spare time, I'll help retest it. Good thinking!

[FlyingIsFun1217]

What is the point of listing them all out on the forum? As you said yourself, it's not hard to do a search on old bugs.

but not everyone do it

Indeed! It also allows to coordinate the effort.

I would say it has the same effect as saying "Hey, I noticed there are 'X' bugs over a year old that have no activity, try checking them out'. Plus, that way you're not making the first post longer than my fairly large monitor.

FlyingIsFun1217

[milon]

Hey gonzoMD, what a great idea! I haven't really ventured into the Bugzilla yet, so thanks for putting this here. I should have some decent free time in a week or two, and I'll test some of these out then.

[DOSGuy]

I would never have guessed that the list was that long if someone hadn't written a post that fills my monitor. And I fully agree that if a bug hasn't been commented on in over a year, there's a high likelihood that it has been resolved by one of the thousands of commits that have gone through since then, or is very similar to some other bug. Closing these bugs will be good for morale, and the bugs that remain will get new attention and maybe finally get fixed. This is a great community initiative.

[wildschwein]

Great idea, posting such a list.

Some of testers needs a concrete task. "Please test this or this bugs...."

There a lot guys out there willing to test, but at the moment the community is there but the grade of conection is not high enough.

Hope this will be significant better with revamp of the webside that i consider as important as the new release.

I dream of different threads for testing tasks, recruiting and helping new tester, show them some tricks for testing, testing seperated in Hardware, VMWare, QEMU etc....with moderators for every subthread....

[gonzoMD]

Great idea, posting such a list.

Some of testers needs a concrete task. "Please test this or this bugs...."

There a lot guys out there willing to test, but at the moment the community is there but the grade of conection is not high enough.

Hope this will be significant better with revamp of the webside that i consider as important as the new release.

I dream of different threads for testing tasks, recruiting and helping new tester, show them some tricks for testing, testing seperated in Hardware, VMWare, QEMU etc....with moderators for every subthread....

I think another important thing for the new website is that the most recent trunk build should be able for download on frontpage too, so the user wouldnt use the old release builds ever and ever, so the most appdb entries are still made for 0.3.13 (just as example).
Or at least a a stable (0.3.14) release cycle as it is and an unstable (0.3.14.1 and so on) every one or two weeks. this would give more attention to this project.
I know (and it was said very often here at the forum too) that version numbers are not important but they represent the actuality of the project to the users.
For example when you visit the WineHQ its nice to see a new version every few weeks, if you visit reactos.org you see that its a year ago. And "Normal" Users doesn't know anything about Trunk Builds and so on.

The Minor Releases could drive on the testing too if you could try to fix one or two bugs per release so the testers would provide more logs because they want a new minor release with even this bugs fixed, its like a dog brings a ball you've thrown away back, because it knows that it gets a dog-cracker.

ok, too much ot talk here back to testing

[milon]

Some of testers needs a concrete task. "Please test this or this bugs...."

Absolutely! Although I don't yet have time for concentrated testing, I poked through the list a bit just to see what they were. Some of them seem very esoteric to me, and I would have no idea how to test them. Could someone give general tips or specific ways to test? This would help many more testers than just me, I think.

I think another important thing for the new website is that the most recent trunk build should be able for download on frontpage too...
Or at least a a stable (0.3.14) release cycle as it is and an unstable (0.3.14.1 and so on) every one or two weeks.

What a great idea!
I know ROS is still alpha, so even the stable releases may not exactly be stable, but it would far better reflect the work & improvement that's taking place.

[gonzoMD]

Could someone give general tips or specific ways to test? This would help many more testers than just me, I think.

you may search for "testcase" in the bugzilla, there are many instructions how to reproduce a bug or little programs that would "force" the bug to appear (if still existing)

or test a specific application

- take an app of your choice, Firefox for example launch it and take notes what doesn't happening well.
- then search for "Firefox" (I think you will get many entries for it) and compare the listed bugs with that what you've found out.
(You say it's esoteric for you, don't read only the headline but the comments too, then everything is a little more understandable in the most cases)
- if you find a difference with an existing bug, just make a comment with your behaviour, your buildnumber and VM/Hardware.
- If there is a bug that isn't encountered at your test, follow the reproduce steps (if avaible) and maybe you can be happy to find a bug that is allready fixed. Comment (again with your specs)that it works for you and the bug will hopefully be closed.
- if you've found an issue not matching to any bugreport just open a new one.

[wildschwein]

Yeah, at the moment it's not that easy to find out, HOW you can help testing.
Testing itself isn't complicated, but you need to know and to find out such a lot of things.

This is preventing new testers from helping perhaps....

But I am convinced that we are on the right way, with the new revamp with drupus managing the webside.
As i read in forum the problem is that with the actual webside the right management couldn't be segmented sufficiently.

In new webside we will have different moderators for every sub-thread ( i hope so...)

I can also take a role as a moderator for newbies in testing on real hardware perhaps....

hope that revamp will come soon.... I am looking forward to that MORE than to new release

[milon]

I may have some time today to go through some of these bugs. Next week I'll have some time as well.

I've tried figuring out how to get a list of bugs that have not been commented in in the past year, and I'm not having success. I'm using an Advanced Search and I've tried a number of options, but no dice. Can someone tell me how to make this magic happen?

[hto]

Can someone tell me how to make this magic happen?

That's easy:

‣ Go to Advanced Search.
‣ To search all bugs (not only bugs in ReactOS itself), unselect ReactOS in Product.
‣ In Status, select UNCONFIRMED to see only these bugs. Or leave it as is to see all active bugs.
‣ In Sort results by, select Last Changed, so the bugs that have not changed for the longest time, will be first in the list.
‣ In Only bugs changed between, leave the first field blank, put 0y into the second field.
‣ Press Search.

To get bugs that have not been changed in the last 2+ years, enter 1y into the 2nd field (w is for weeks, d is for days). And so on.