EA/DICE respond to backlash
... https://www.reddit.com/r/battlefield2042/comments/rx0w9y/eadice_finally_responds_to_the_backlash/?utm_medium=android_app&utm_source=share
Forum Discussion
@Psubond With 10 digits, even automation may take too long and be cost prohibitive long before the 'magic' combination is hit.
At the end of the day though, it was a simplified example to highlight the difficulties in QAing complex software.
Even an extended Beta may not highlight some/all of the bugs so far encountered.
At the end of the day though, it was a simplified example to highlight the difficulties in QAing complex software.
Even an extended Beta may not highlight some/all of the bugs so far encountered.
@Trokey66 wrote:
@PsubondWith 10 digits, even automation may take too long and be cost prohibitive long before the 'magic' combination is hit.
At the end of the day though, it was a simplified example to highlight the difficulties in QAing complex software.
Even an extended Beta may not highlight some/all of the bugs so far encountered.
i never said that it would find ALL of the bugs and i truly hope you are not trying to make the case that because it's hard to QA a game they shouldn't bother.
as for the button testing a human wouldn't be faster and not doing it is unacceptable.
multiple computers running the test to split up the work means it would not take that long. you aren't trying to break 256 bit encryption, you are testing button press combos and you don't need to build a robot that actually pushes buttons you just need to send the button presses to the xbox/ps/pc via an interface instead of a controller (yes, we don't have them but i'm sure the devs do. there is no way they have to have an actual person do everything)
- @Psubond When did I say the shouldn't bother?
Testing complex software is often carried out on a risk based cost/benefit basis depending on the criticality of the specific software.
All your examples come at a cost that may be deemed excessive for the development team.- @Trokey66 Holy crap im just saying your example wasnt great not trying to fight. Im simply pointing out that automating a button press test is a few lines of code to iterate through all possible combos.
- @Psubond Neither m I but it not just automating the button presses is it?
The 'few lines of code' have to do all possible combinations (how long will that take with 10 digits?).
The 'few lines of code' then have to monitor the results.
The 'few lines of code' have to be able to record any errors.
The 'few lines of code' then have to identify the cause of errors.
The 'few lines of code' must also be validated and approved before use.
My point is, even a 'simple test' is not always as simple as it may seem and takes time and money.
Featured Places
