Jump to content

Search the Community

Showing results for tags 'spot-check'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Welcome Aboard
  • Kerbal Space Program 1
    • KSP1 Discussion
    • KSP1 Suggestions & Development Discussion
    • KSP1 Challenges & Mission ideas
    • KSP1 The Spacecraft Exchange
    • KSP1 Mission Reports
    • KSP1 Gameplay and Technical Support
    • KSP1 Mods
    • KSP1 Expansions
  • Kerbal Space Program 2
    • KSP2 Dev Updates
    • KSP2 Discussion
    • KSP2 Suggestions and Development Discussion
    • Challenges & Mission Ideas
    • The KSP2 Spacecraft Exchange
    • Mission Reports
    • KSP2 Prelaunch Archive
  • Kerbal Space Program 2 Gameplay & Technical Support
    • KSP2 Gameplay Questions and Tutorials
    • KSP2 Technical Support (PC, unmodded installs)
    • KSP2 Technical Support (PC, modded installs)
  • Kerbal Space Program 2 Mods
    • KSP2 Mod Discussions
    • KSP2 Mod Releases
    • KSP2 Mod Development
  • Community
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
    • KSP Fan Works
  • International
    • International

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


About me


Location


Interests

Found 1 result

  1. I'll admit that I'm clueless on QA in general, and particular about how it's done at Intercept Games. However, as my day job requires me to create financial reports covering large amounts of money (let's just say that I need to adjust the column width in Excel to fit the numbers in the output) I do have some experience in quality checking, and from my laymen, Monday Morning Coach, Captain on the Quay viewpoint it seems some checks are being skipped. See, I know what to look for.. Discrepancies by week, month, product, and a couple of other dimensions. So my quality checks look at those. But there are always the things you don't look for. So, I pull out the detail reports for our top-5 customers, and for another random 5. And that's the step that's missing with KSP2 QA. Run a handful of extended play-through scenarios: Build a ship from scratch in the VAB, launch it, put it in orbit Build another ship from scratch, launch it, dock with the first one Undock both ships and return to Kerbin Build a ship, launch, and land it on Mun, plant a flag, and return to Kerbing Build a ship, launch it, and land it on Minmus, plant a flag, and return to Kerbin Build a ship, launch it, land it on Duna, plant a flag, and return to Kerbin Between those 5 builds you can cover a wide variety of parts. And granted while not covering all situations and scenarios, it will cover a lot of ground. Current testing seems to focus on prescribed scenarios bound to known errors, and for time saving purposes those are either pre-saved or set up using a "cheat" dialog. And that's ok. You want to know if bug #684 has been addressed in all 12 known scenarios, and there's hundreds of cases you have to go through. But clearly, clearly, the vital act of "spot-checking" — in this case just playing the game — is not performed right now. Or if it is, some people need to get fired. There are just too many bugs in the game to believe a serious effort is made in that direction. If there is play testing, then why do we now have a hotfix for the fairing UI bug in the VAB. HOW WAS THAT MISSED? Fairings respawning on engine plates every. single. time. How could someone not see this and report this? Please. Add a handful of actually playing the game to the test book.
×
×
  • Create New...