如何引入网络应用程序
我运行一个游戏，运行是手动完成的，我有一些脚本可以帮助我，但本质上是我在做这项工作。 我目前正在开发网络应用程序，该应用程序将允许用户直接输入他们的一些游戏操作，从而节省我很多工作。
问题是，我一个人在一个中等规模（20 个表以上）的项目上工作，工作量不是问题，问题是即使我边写边测试，错误也会出现。 所以我的问题有两个方面。
- Beta 测试，我喜欢公开 Beta 测试，但是封闭 Beta 测试是否会更有效并提供更好的结果？
- 我应该如何引入该应用程序？ 我应该一回合将其放入并声明它正在使用，还是应该将它与游戏的正常结构一起使用？
I run a game and the running is done by hand, I have a few scripts that help me but essentially it's me doing the work. I am at the moment working on web app that will allow the users to input directly some of their game actions and thus save me a lot of work.
The problem is that I'm one man working on a moderately sized (upwards of 20 tables) project, the workload isn't the issue, it's that bugs will have slipped in even though I test as I write. So my question is thus two-fold.
- Beta testing, I love open beta's but would a closed beta be somehow more effective and give better results?
- How should I bring in the app? Should I one turn drop it in and declare it's being used or should I use it alongside the normal construct of the game?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这是我测试/启动的一般方法。
您的测试/启动方式主要取决于：
如果您的应用程序是技术应用程序并且面向技术型应用程序，那么“测试版”一词不会真正吓到他们，而是提供了在产品“上线”之前测试产品的机会，并有助于改进系统。 这是使用公开测试版或封闭测试版的理想情况。 通常，与您选择并信任的一组人开始“封闭”，以便快速可靠地查找错误 - 在您更有信心所有关键错误都消失后，使用邀请系统将其打开（例如）。
然而，如果您的应用程序从技术角度来看是“微不足道的”（即，它类似于 Twitter、Facebook 或 Flickr - 没有什么本质上适合技术使用），那么您将必须更加小心您计划您的测试。 封闭式测试绝对是您的第一个选择，并且这应该比更“技术”产品的封闭式测试持续更长时间。 原因？ 你的“普通人”不一定知道“beta”这个词的含义，其他人很可能会被它吓到，或者过早地判断你的服务（不理解这个“公共测试”阶段的概念）。 许多人不想被用作小白鼠。
This is my general approach to testing/launching.
How you test/launch depends mostly on:
If you application is a technical application and is geared to the technically-minded, the word "beta" won't really scare them - but provide an opportunity to test the product before it goes 'live', and help to improve the system. This is the ideal circumstance in which to use either an open or closed beta. It's usually beneficial to start off 'closed' with a group of people you select and trust to bug-find quickly and reliably - after you're more confident that all the critical bugs are gone, open it up with an invite system (for example).
If, however, your application is 'trivial' from a technical standpoint (i.e. it's something like Twitter, or Facebook, or Flickr - nothing that is inherently geared towards technical usage), then you're going to have to be more careful in how you plan your testing. Closed testing is most definitely your first port of call, and this should last for longer than a closed beta on a more 'technical' product. The reason? Your 'average Joe' doesn't necessarily know what the word "beta" means, and others may well be scared by it, or judge your service prematurely (not understanding the concept of this 'public testing' phase). Many won't want to be used as guinea pigs.
我不明白你所说的“引入应用程序”和“一圈放下它”是什么意思。 “引入应用程序”是指部署吗？ 至于“一转落”，我完全不明白。
至于公开测试版，这实际上取决于您的受众。 例如，《反恐精英》显然在进行公开测试之前先运行了一些封闭测试，所以我的建议是：
这与 StackOverflow 采取的方法类似，但将其设置在游戏论坛上的游戏将带来双重好处：为您的游戏做广告并吸引一些感兴趣的 Beta 测试者。
I don't understand what you mean by "bring in the app" and "one turn drop it". By "bring in the app" do you mean deploy? As for "One turn drop", I totally don't understand it.
As for open betas, that depends on your audience, really. Counterstrike, for example, apparently run a few closed betas before doing open betas, so here's my suggestion:
This is similar to the approach StackOverflow took, but this being a game setting it up on a gaming forum will give the dual benefit of advertising your game and getting some interested beta testers.
我将尝试用您提供的有限详细信息来回答。
1：只有当您引起轰动，并且有一大群用户敲响您的大门，试图参与其中时，它是开放还是关闭才真正成为一个问题。
如果是这样的话，我认为您可能会在内测版中获得更多用户的忠诚度和承诺。
2：你没有给出很多（任何）细节来说明你在谈论什么类型的游戏，所以很难回答这个问题。
/乔纳斯
I'll try to answer with the limited amount of details you've given.
1: Wether it's open or closed is really only an issue if you have great buzz, and a large group of users hammering down your door, trying toget in on the action.
If this is the case, I think you might get more loyalty and commitment from users in a closed beta.
2: You haven't given many (any) details as to what kind of game you are talking about, so it's pretty hard to answer this one.
/Jonas