128 pages of bug reports? Really FDEV?....................................

Good grief.

Please............................ play your own game before releasing patches which are doomed to bug reporting on this sort of scale.
 
The server error when restocking is particularly bad. Bugs aren't subjective sadly.

Apparently the new lady on the lifestreams is the project manager for all of elite.. maybe someone in the live audience can pop in a question live to get some insight on whats going on behind the scenes would be great.

There's either no testing or bugfix cycles, or epic differences between production, test and development enviroments they haven't bothered to make whole yet.
 
Usually development companies have regression testing, which is a set of normally automated tests to confirm existing core functionality after changes have been added.
The problem with large scale developments, of which Elite is an example, is that there are far too many scenarios to cater for in this type of testing.

This is why beta tests are so commonly used, as the unpredictable usage of a high number of players will often expose many issues that wouldn't have become apparent through internal play testing. I don't know why Frontier did not run a beta on this, but I suspect that after what has occurred, the next minor update will likely include a beta period.
 
Frontier have released patches to Elite Dangerous before, many considerably larger. They aren't completely "green"....

Well if they weren't green before, then they're properly blooded now. I think the April update drove home the importance of beta testing, even for small updates.
I suspect they considered it minor enough not to require a beta period, but hopefully they've learned the mistake of having this overconfidence.
 
They are multiples of the same bugs which I'm sure swell the numbers. I know that there were for one I reported.

I hardly ever report bugs anymore, someone has already done the job before me.

Yeah it wouldn't make any sense, it's better to add a contribution to the existing bug so it can be promoted to the next stage
 
Good grief.

Please............................ play your own game before releasing patches which are doomed to bug reporting on this sort of scale.
Please ... Learn about how all bug reporting systems fill up with trash, dupes, support requests if not managed. Only failing here is there failing to manage the reports.
 
You have to remember a lot are duplicate bugs or really old threads LOL.

My mate game/play tests for Splash Damage... most games are full of hundreds of bugs or errors you just never notice or seem them. Bit of a trolling thread OP!
 
Usually development companies have regression testing, which is a set of normally automated tests to confirm existing core functionality after changes have been added.
The problem with large scale developments, of which Elite is an example, is that there are far too many scenarios to cater for in this type of testing.

This is why beta tests are so commonly used, as the unpredictable usage of a high number of players will often expose many issues that wouldn't have become apparent through internal play testing. I don't know why Frontier did not run a beta on this, but I suspect that after what has occurred, the next minor update will likely include a beta period.
Yup, the "shields get re-enabled when entering SC" bug is a good for example that. I never disabled my shields in Elite, and while I am sure there are reasons why people are doing it, I'd guess it's only a small number of players who regularly fly with disabled shields... I can't blame QA for missing that one.
 
Back
Top Bottom