One thing I've learned about testing is to write code at the same speed you write the tests. This way your code will have full coverage and in the future when you have a game hte size Minecraft is today, it'll be much simples to identify erros and fix them, leaving more time to add new features rather then fix bugs.
But this must de done from the beginning, or else you would have to spend days creating tests, and no one will do that because the game must continue being developed.
Bugs happen, then your compiler finds half of them, then your unit tests find half of the remainder, then you run the software and see if it works yourself and find half of the remainder again. Before anyone except the developer themselves have seen it, about 88% of bugs are gone and only 12% are left.
You skip unit testing or skip your own "run it and see" tests and you end up with 25% of bugs left in the code. You skip both of these and 50% of bugs get left in the code.
Nobody makes bugs on purpose. Professional developers do find/fix bugs on purpose though, which includes unit testing. Amateur/hobbyists developers slap stuff together and cross their fingers. Given the ongoing rate of bugs (and given that 1.6 was intended to be a "mostly bugfixes" release), on a scale from 1 to 10 (1 being "amatuer" and 10 being "professional"), how would you rate the last few releases?
with minecraft doing a hard crash every fifteen minutes and being unable to light any new underground structures, i guess i'd like to see some kind of official response regarding how mojang handles testing internally and what warrants an external beta update versus an internal build update since it's become an actual software company.
if someone has any insight into this, feel free to shed some light on how/why minecraft is publicly updated.
because issues can happen everywhere, which is why real software companies do intensive regression testing all the time.
Not in beta tests. Not most of the time anyhow. That sort of rigorous testing is reserved for release builds. This is a beta test. Get the hell over it already. It's gonna have bugs, and they are going to miss things. You aren't entitled to a perfectly working game until it's done.
There obviously is testing going on, since you're participating in it. The game's in beta testing right now. Since the game isn't released until 11/11/11, if you're playing it today, it's proof positive that there is indeed testing going on, and you're one of the testers. Have fun! :smile.gif:
Which wouldn't be so bad if the Mojang team were either active in the forum taking note of the bugs found or had a site of their own where we could directly contact them about bugs we find. There's little point in being a beta tester if the makers aren't listening.
i dont think ANYTHING gets tested. even bug fixes. for example, the fix for glass, which just made the bug worse and effect everything else, and the other 5 failed bug fixes.
Which wouldn't be so bad if the Mojang team were either active in the forum taking note of the bugs found or had a site of their own where we could directly contact them about bugs we find. There's little point in being a beta tester if the makers aren't listening.
There is a site. The get satisfaction site has a bug report option. Also in a tweet Notch or Jeb (I can't remember who) said they read the buglist on the wiki found here. http://www.minecraft...Version_history
Rollback Post to RevisionRollBack
This will sit here for inspiration for Proloe to update!!
There is a site. The get satisfaction site has a bug report option. Also in a tweet Notch or Jeb (I can't remember who) said they read the buglist on the wiki found here. http://www.minecraft...Version_history
whats the last time a bug report from getsatisfaction was fixed (aside from false bug fixes)? and why minecraftwiki was discovered months after it came online?
Not in beta tests. Not most of the time anyhow. That sort of rigorous testing is reserved for release builds. This is a beta test. Get the hell over it already. It's gonna have bugs, and they are going to miss things. You aren't entitled to a perfectly working game until it's done.
i'm not expecting a perfectly working game, but it's highly unprofessional to release a build that's as broken as 1.6 was. as an internal build, that's fine, but for a public release it is definitely not.
also what you said just isn't true for decent software companies.
But this must de done from the beginning, or else you would have to spend days creating tests, and no one will do that because the game must continue being developed.
THIS
Bugs happen, then your compiler finds half of them, then your unit tests find half of the remainder, then you run the software and see if it works yourself and find half of the remainder again. Before anyone except the developer themselves have seen it, about 88% of bugs are gone and only 12% are left.
You skip unit testing or skip your own "run it and see" tests and you end up with 25% of bugs left in the code. You skip both of these and 50% of bugs get left in the code.
Nobody makes bugs on purpose. Professional developers do find/fix bugs on purpose though, which includes unit testing. Amateur/hobbyists developers slap stuff together and cross their fingers. Given the ongoing rate of bugs (and given that 1.6 was intended to be a "mostly bugfixes" release), on a scale from 1 to 10 (1 being "amatuer" and 10 being "professional"), how would you rate the last few releases?
if someone has any insight into this, feel free to shed some light on how/why minecraft is publicly updated.
Not in beta tests. Not most of the time anyhow. That sort of rigorous testing is reserved for release builds. This is a beta test. Get the hell over it already. It's gonna have bugs, and they are going to miss things. You aren't entitled to a perfectly working game until it's done.
Which wouldn't be so bad if the Mojang team were either active in the forum taking note of the bugs found or had a site of their own where we could directly contact them about bugs we find. There's little point in being a beta tester if the makers aren't listening.
http://www.minecraftforum.net/viewtopic.php?f=1&t=23440
There is a site. The get satisfaction site has a bug report option. Also in a tweet Notch or Jeb (I can't remember who) said they read the buglist on the wiki found here. http://www.minecraft...Version_history
whats the last time a bug report from getsatisfaction was fixed (aside from false bug fixes)? and why minecraftwiki was discovered months after it came online?
http://www.minecraftforum.net/viewtopic.php?f=1&t=23440
i'm not expecting a perfectly working game, but it's highly unprofessional to release a build that's as broken as 1.6 was. as an internal build, that's fine, but for a public release it is definitely not.
also what you said just isn't true for decent software companies.