Why Closed (Not Reproducible)

Why cases are closed as Not Reproducible when sometimes the behavior is no longer present on a pre-release version? Why not mark that as fixed on next release?

I have seen sometimes that cases are closed with the following legend:

I understand that maybe this problem was fixed by fixing something else, but if the current release has the problem and an upcoming release doesn’t, well the case is fixed anyway, no?

If the developers can not say for sure if a bug has been fixed, the case should remain open or closed as non-reproducible. Claiming that a bug has been fixed just because it is not reproducible as before can also be dangerous. :wink:

Well, the case is easy reproducible with the current release and several previous releases (bug). If it is not reproducible on a future release, then is fixed, no?

Not reproducible is just that - a statement saying the tester could not reproduce the issue noted given the steps
Doesn’t mean “fixed”
It’s just “I cant make it behave like that”
And if you happen to find a way to reproduce it the case can be reopened
see feedback://showreport?report_id=50509 which had that sequence of events happen and the case is now reproduced

Maybe, but not for sure.

Thank you Norman, I understand that. My only “problem” is that some cases are closed as not reproducible using a not released version, when most cases are easily reproducible with current latest release.

Maybe it is only a technicality, but closing a bug report for the current release as ‘not reproducible’, at least for me, should be when the developers can’t reproduce the issue with the current release.

Ok, maybe but not for sure. Then why close it if the current release is easily reproducible (see above) and the developers don’t know for sure if it is fixed.

Anyway, I think my idea is not clear. Thank you for your comments.

Let me try one last time to explain my idea:
I think Closed (Not Reproducible) should be used only with released versions. If I report a bug on the current released version and is easily reproducible, should be open and marked as reproducible. Then if the developers change some code for other thing and release a new version that doesn’t have this issue, not because they actually changed specific code for this problem but other changes made this issue ‘go away’, then the case can be closed as not reproducible in version XXX and not mention a ‘newer version of the IDE’.

What happen if they change more code and this issue come back at release time? Then we need to ask to reopen the case because the newer newer version of the IDE show the same problem.

Because the circumstances have changed. Maybe the reproduction steps changes. It’s disingenuous to say the bug was fixed when it wasn’t confirmed in the first place and that specific actions taken corrected the bug.

New case with this “not reproducible”:
feedback://showreport?report_id=56044
but then Greg opened a new case exactly with the same information:
feedback://showreport?report_id=56060

Why Greg took the time to open a case for a current release if they are working on a new release that doesn’t have this issue?

Of course Xojo can do whatever they want, but for me, they just need to wait for a newer release to hit the public to close this type of cases, I don’t understand why they close them before a public release.

It would take a lot more staff to do what you describe (wait for new release).

It is a lot more effective with a small team to reopen if needed.

I’ve had this response to a case “This case has been closed because our testing staff has been unable to reproduce the behaviour using a newer version of the IDE.” due to me reporting it fixed in a unreleased alpha. I’m guessing that will be one less bug fix for stats.

[quote=441602:@Alberto De Poo]New case with this “not reproducible”:
feedback://showreport?report_id=56044
but then Greg opened a new case exactly with the same information:
feedback://showreport?report_id=56060

Why Greg took the time to open a case for a current release if they are working on a new release that doesn’t have this issue?

Of course Xojo can do whatever they want, but for me, they just need to wait for a newer release to hit the public to close this type of cases, I don’t understand why they close them before a public release.[/quote]
The reason it was closed was the tester looked at our 2019r2 builds, but didn’t understand that the problem only manifests in point releases. I knew I’d seen a mention of it somewhere, but I couldn’t remember where and Feedback won’t let you search for anything less than three characters, so it didn’t come up in my search. Our internal system requires us to have an open case to check in a fix so we’re always sure that there’s a reason for doing so. I closed my case as a duplicate of and reopened the first one.