
By NearTao
Sat May 23, 2020 1:11 pm

Still... 2.8.1 will hopefully address some of these imperfections


NearTao wrote:
Still... 2.8.1 will hopefully address some of these imperfections

Eyalc wrote:They need to do two things or else this is going to happen constantly:
1. Fix the foundation. When you add things on a shaky foundation, this is the result.
2. Expand the testing coverage. No way something like this shouldn't have been caught in a beta test. It's almost like all of the testers have the exact same workflow and usage patterns. If so, they need to expand.
Eyalc wrote:They need to do two things or else this is going to happen constantly:
1. Fix the foundation. When you add things on a shaky foundation, this is the result.
2. Expand the testing coverage. No way something like this shouldn't have been caught in a beta test. It's almost like all of the testers have the exact same workflow and usage patterns. If so, they need to expand.
NearTao wrote:Eyalc wrote:They need to do two things or else this is going to happen constantly:
1. Fix the foundation. When you add things on a shaky foundation, this is the result.
2. Expand the testing coverage. No way something like this shouldn't have been caught in a beta test. It's almost like all of the testers have the exact same workflow and usage patterns. If so, they need to expand.
Personally, I'm less concerned that a regression happened... and more concerned that it doesn't seem to have been acknowledged in a meaningful way, and Akai is not really good at explaining what they will do to make sure the regression doesn't happen again.
but that's my two cents.
Lumi wrote:Eyalc wrote:They need to do two things or else this is going to happen constantly:
1. Fix the foundation. When you add things on a shaky foundation, this is the result.
2. Expand the testing coverage. No way something like this shouldn't have been caught in a beta test. It's almost like all of the testers have the exact same workflow and usage patterns. If so, they need to expand.
I think beta testing is not working so good.
I mean, there are some issues that a good beta tester should notice in a minute, like the conflict between the qlink overlay and the data dial.
Maybe they didn't have time to test all? They were focused on checking multimidi?
I don't know but before releasing an update, you first have to check if all that worked is still working as before.
Take a look at getsatisfaction forum, there is a huge list of people having problems with 2.8 and mrs. Eliza is not replying anymore.
Lumi wrote:I just wonder if they checked this before releasing the update or just made all in a rush to put it on Live2 the day of its release.
Eyalc wrote:Lumi wrote:I just wonder if they checked this before releasing the update or just made all in a rush to put it on Live2 the day of its release.
I think this is probably right.
But I don't see why though. There's nothing on the Live 2 that make these features more desirable / required.
But, such is Akai.

Eyalc wrote:They need to do two things or else this is going to happen constantly:
1. Fix the foundation. When you add things on a shaky foundation, this is the result.
2. Expand the testing coverage. No way something like this shouldn't have been caught in a beta test. It's almost like all of the testers have the exact same workflow and usage patterns. If so, they need to expand.

Lampdog wrote:There should be a test sheet with PRECISE functions and steps to check off.
Lampdog wrote:Eyalc wrote:They need to do two things or else this is going to happen constantly:
1. Fix the foundation. When you add things on a shaky foundation, this is the result.
2. Expand the testing coverage. No way something like this shouldn't have been caught in a beta test. It's almost like all of the testers have the exact same workflow and usage patterns. If so, they need to expand.
There should be a test sheet with PRECISE functions and steps to check off.
Monotremata wrote:Lampdog wrote:There should be a test sheet with PRECISE functions and steps to check off.
When Ive done internal beta testing, we were always given scripts to use to attempt to break things and test functionality. The public beta testing Ive done, there wasn't anything to it. I remember both Wave Arts and FXPansion just gave out apps/plugins and said 'Here you go let us know if you have any problems' but nothing specific to look at or try out. If you used a limited feature set in one that worked for you, you may never encounter bugs so they'll go completely unreported.

Eyalc wrote:This is what I think the problem is.