With the release date, being the 11th.... this is a concern!

Trellek

T
Fair point. But my comment was not about fault. I was commenting that it is the qa’s team job to ensure bugs are reported and addressed.

If they cannot do their job, for whatever reason, the fundamental problem does not change.

The fact that there is not sufficient emphasis on QA and bugs has been an issue since the start, and should be every players concern.

Whilst in general I disagree with players getting upset because the feature they want is not being developed (eg spacelegs, or more involved missions, etc), I do think that players have a right to demand fixes, or at least aknowledgement of the effort put in logging a fix request.
 

Thatchinho

Thatchinho
Stealthie said:
I'd assume that, behind the scenes, FDev list all the NEW bug-reports from the beta and they've got to a point where most of the bugs currently being reported are duplicates of stuff they already know about.

Week 1: 500 bugs/week are being reported and they're ALL (obviously) new. (total: 500 bugs)
Week 2: 500 bugs/week are being reported and 50% of them are new and the rest are duplicates. (total: 750 bugs)
Week 3: 500 bugs/week are being reported and 10% of them are new and the rest are duplicates. (total: 800 bugs)
Week 4: 500 bugs/week are being reported and 1% of them are new and the rest are duplicates. (total: 805 bugs)

By this point, they've had 3 weeks to work on 800 of those bugs - many of which are simple oversights - so it's entirely likely most of them WILL be fixed.

Sure, ideally you'd just keep testing until 0% of bug reports were new but that's not really realistic, especially in this age of online-only games where hot-fixes can be applied automatically.
Click to expand...
Not sure how involved you were with the Beta, so you might have already taken into account, but if not, it's worth bearing in mind that there were various stages to the Beta, and each stage added extra functionality which wasn't part of the previous stages and wouldn't have had any bug reports from it. Also another factor is the depth of people's involvement. Some will have focussed heavily on specific areas when they were released, and not had much involvement at other points.

Each update to the Beta also brought various bug fixes from the previous stages.

I'd say that the number of duplicates reports probably decreased as things went on. For example at the first stage of the Beta, a lot of issues were around the controls/bindings. They could be worked around but effected everyone to a greater or lesser degree until they were fixed. As the wider issues get fixed, it enables people to concentrate on checking other things.

What it effectively means is the serious stuff that effects everyone tends to have been dealt with, as it was flagged up en-masse in the early days.

Serious things effecting smaller groups tend to have also been dealt with.

More minor things that effect everyone also tend to have been dealt with.

As that happens, it becomes more and more about detailed specific bugs, some of which are tied to specific circumstances which aren't notices until you're in those circumstances. Which then become harder and harder to replicate, and so on.

I checked the Beta Bug Report forum fairly often, and added to other people's bug reports if I saw ones that I'd encountered but hadn't reported, and others were obviously doing similar too.

From those checks, I didn't envy QA their task in dealing with it all.

I've got a load of open Bug Reports, and IMHO, the generic response that's been coming through latterly is actually pretty reasonable and appropriate under the circumstances.
 

Thatchinho

Thatchinho
Rambojambo said:
How is that inconsistent to my assertion? You've just admitted they can't fulfil the requirement of a QA team.
Click to expand...
The requirement? It's not always possible to always deliver platinum standards on every thing that every person thinks is a requirement of a team. Sometimes things have to give.

As it stands this is fuss over people getting a generic response (which works under the circumstances) rather than specific tailored responses. It's not exactly the worst thing to have ever happened.
 

gooddoc

gooddoc
Bugs???

Try playing X4! I basically save it before each button press, in case I get a CTD, then the damn 'Steam' kicks in & syncs the files for a hour b4 I can load it again!!

I'v yet to really come across any bugs in ED. I find it runs really well, even the Beta. I can't recall the last time I had a CTD it was that long ago. Frontier do a marvelous job.

I sometimes think that others are playing a different version of ED than what I am, with the 'game breaking' bugs they keep reporting on the forums.
 

Factabulous

Factabulous
gooddoc said:
I'v yet to really come across any bugs in ED. I find it runs really well, even the Beta. I can't recall the last time I had a CTD it was that long ago. Frontier do a marvelous job.
Click to expand...

The Beta this time did have some good ones - every time I died in an AX CZ I had a CTD on rebuy, which was fun :) But then again that is the reason for the beta, and as you say I very rarely have CTD in the Live gaime.

gooddoc said:
I sometimes think that others are playing a different version of ED than what I am, with the 'game breaking' bugs they keep reporting on the forums.
Click to expand...

Well, if you consider NPC pad-squatting* as a major bug (as some seem to) then ....

* Not that I've even seen that bug, just as I never got hit by the skimmer rain, and both certainly do/did exist
 

gooddoc

gooddoc
Factabulous said:
The Beta this time did have some good ones - every time I died in an AX CZ I had a CTD on rebuy, which was fun :) But then again that is the reason for the beta, and as you say I very rarely have CTD in the Live gaime.



Well, if you consider NPC pad-squatting* as a major bug (as some seem to) then ....

* Not that I've even seen that bug, just as I never got hit by the skimmer rain, and both certainly do/did exist
Click to expand...

I never came across either of those bugs, even though I was aware of & looked out for them.....maybe Iv been lucky over these last 4 years & managed to steer clear of these issues.

I did get stuck at Deciat though in the Beta, I just waited for a couple of days for the beta update & carried on.
 

DeletedUser191218

D
Thatchinho said:
The requirement? It's not always possible to always deliver platinum standards on every thing that every person thinks is a requirement of a team. Sometimes things have to give.

As it stands this is fuss over people getting a generic response (which works under the circumstances) rather than specific tailored responses. It's not exactly the worst thing to have ever happened.
Click to expand...

Specific, tailored responses? Are you serious? Just a response to the darn ticket for crying out loud. "Dunno if it's fixed, you tell us" is not a good service level. You sound silly now. Stop it.
 

Stigbob

Stigbob
Rambojambo said:
I think the QA team should be able to advise whether or not it's been fixed mate. That's their job.
Click to expand...

Its also their job not to waste time and effort on issues no longer relevant as they only existed in a beta and they are moving on with the release.
 

Thatchinho

Thatchinho
Rambojambo said:
Specific, tailored responses? Are you serious? Just a response to the darn ticket for crying out loud. "Dunno if it's fixed, you tell us" is not a good service level. You sound silly now. Stop it.
Click to expand...
I'm sounding silly? Ha ha ha! Well you do seem to hear whatever you want to hear, so I'm not surprised to see you say something like that.

Everyone is getting a response to their tickets. There is nothing about people not getting a response, so where are you getting "Just a response to the darn ticket for crying out loud." from. This is just about the nature of the response.

In the context, the generic response is reasonable and appropriate. I'm saying that from various perspectives, including that of being someone whose spent a lot of time in the Beta checking things, documenting and submitting bug reports, and is getting the very response you're unhappy about.

Various bug I've reported have already been fixed. Nothing more is needed on those. I don't need a response to the posts telling me they've been fixed. I know they've been fixed because they are no longer happening. We don't need to go through a closing process. It's fine. Any time spent by QA telling me they're fixed is a waste of time.

Various others haven't yet been fixed, but some of them will be when 3.3 launches. I will know fairly soon after 3.3 launches whether they have been fixed. Where they've been fixed, then nothing more is needed from either me or QA, and any other action is not needed.

Some won't be fixed. There's one at least that was a specific set of circumstances that is unlikely to be replicated, which I reported in case it was symptomatic of something. I doubt I'll be able to replicate it, so am unlikely to re-report it.

Any others that still occur, if they are material enough to be worth it, I will raise another bug report.

Oh, and I've got one where I don't know if it's a bug or working as intended. I've asked for it to be clarified so that I know whether to check or not, and QA have passed it on to be checked.

I did not do all that testing, documenting and reporting so that I could get attention and responses from QA. I did it so that issues could be identified and where reasonable, resolved.

There is no need for QA to waste any time on replying in any more detail then they have. That is time they could be spending on more productive things in the limited time before Release.

There's some things which other people have raised which may warrant more of a reply, but that is the exception not the rule.

There is no need for any fuss.

Again, this it is not about Live (and I am saying this here because of what you've been saying about maintenance and service levels), it is about a Beta.
 

CMDR MRMAURICE

CMDR MRMAURICE
Thatchinho said:
I'm sounding silly? Ha ha ha! Well you do seem to hear whatever you want to hear, so I'm not surprised to see you say something like that.

Everyone is getting a response to their tickets. There is nothing about people not getting a response, so where are you getting "Just a response to the darn ticket for crying out loud." from. This is just about the nature of the response.

In the context, the generic response is reasonable and appropriate. I'm saying that from various perspectives, including that of being someone whose spent a lot of time in the Beta checking things, documenting and submitting bug reports, and is getting the very response you're unhappy about.

Various bug I've reported have already been fixed. Nothing more is needed on those. I don't need a response to the posts telling me they've been fixed. I know they've been fixed because they are no longer happening. We don't need to go through a closing process. It's fine. Any time spent by QA telling me they're fixed is a waste of time.

Various others haven't yet been fixed, but some of them will be when 3.3 launches. I will know fairly soon after 3.3 launches whether they have been fixed. Where they've been fixed, then nothing more is needed from either me or QA, and any other action is not needed.

Some won't be fixed. There's one at least that was a specific set of circumstances that is unlikely to be replicated, which I reported in case it was symptomatic of something. I doubt I'll be able to replicate it, so am unlikely to re-report it.

Any others that still occur, if they are material enough to be worth it, I will raise another bug report.

Oh, and I've got one where I don't know if it's a bug or working as intended. I've asked for it to be clarified so that I know whether to check or not, and QA have passed it on to be checked.

I did not do all that testing, documenting and reporting so that I could get attention and responses from QA. I did it so that issues could be identified and where reasonable, resolved.

There is no need for QA to waste any time on replying in any more detail then they have. That is time they could be spending on more productive things in the limited time before Release.

There's some things which other people have raised which may warrant more of a reply, but that is the exception not the rule.

There is no need for any fuss.

Again, this it is not about Live (and I am saying this here because of what you've been saying about maintenance and service levels), it is about a Beta.
Click to expand...

You forgot to.... drop the mic :p
 

Rafe Zetter

Banned
Rafe Zetter
Factabulous said:
How is this different from usual? And you haven't quit yet OP :)

Every new release some get 'worried' that all the 'bugs' won't be fixed. Every release FDev ship once (most of) the crashes are fixed. Every release goes ok. Circle of life :D
Click to expand...

"Every release goes ok."

stretching things a little aren't we?

But yes in this case I can understand that FDev are under the gun and can't truly be expected to give each bug report an individual reply, or make assurances that all will be sorted in 4 days time.
 

DeletedUser191218

D
Thatchinho said:
I'm sounding silly? Ha ha ha! Well you do seem to hear whatever you want to hear, so I'm not surprised to see you say something like that.

Everyone is getting a response to their tickets. There is nothing about people not getting a response, so where are you getting "Just a response to the darn ticket for crying out loud." from. This is just about the nature of the response.

In the context, the generic response is reasonable and appropriate. I'm saying that from various perspectives, including that of being someone whose spent a lot of time in the Beta checking things, documenting and submitting bug reports, and is getting the very response you're unhappy about.

Various bug I've reported have already been fixed. Nothing more is needed on those. I don't need a response to the posts telling me they've been fixed. I know they've been fixed because they are no longer happening. We don't need to go through a closing process. It's fine. Any time spent by QA telling me they're fixed is a waste of time.

Various others haven't yet been fixed, but some of them will be when 3.3 launches. I will know fairly soon after 3.3 launches whether they have been fixed. Where they've been fixed, then nothing more is needed from either me or QA, and any other action is not needed.

Some won't be fixed. There's one at least that was a specific set of circumstances that is unlikely to be replicated, which I reported in case it was symptomatic of something. I doubt I'll be able to replicate it, so am unlikely to re-report it.

Any others that still occur, if they are material enough to be worth it, I will raise another bug report.

Oh, and I've got one where I don't know if it's a bug or working as intended. I've asked for it to be clarified so that I know whether to check or not, and QA have passed it on to be checked.

I did not do all that testing, documenting and reporting so that I could get attention and responses from QA. I did it so that issues could be identified and where reasonable, resolved.

There is no need for QA to waste any time on replying in any more detail then they have. That is time they could be spending on more productive things in the limited time before Release.

There's some things which other people have raised which may warrant more of a reply, but that is the exception not the rule.

There is no need for any fuss.

Again, this it is not about Live (and I am saying this here because of what you've been saying about maintenance and service levels), it is about a Beta.
Click to expand...

Tl dr.
 

Factabulous

Factabulous
CR33P said:
Unless you're the ONLY person to have reported that bug, there's a good chance it's already being addressed
Click to expand...

someone else who raised no bugs on the beta and has an opinion on how FDev deal with bug reports....

Edit: Then again, half the posts in here start with 'I don't play anymore but...', so why not ;)
 
You must log in or register to reply here.
Back
Top Bottom