您使用什么工具来管理 Web 应用程序的 Beta 测试人员?

发布于 2024-09-24 08:03:36 字数 515 浏览 4 评论 0原文

如果这是在错误的地方,请原谅我,但我认为一些程序员可能对测试他们的代码有一些想法。

我已经编写了一个 Web 应用程序,将在一小部分受众 (10-20) 中进行 beta 测试,并最终为 iOS 平台开发一个应用程序。

我正在寻找一个可以帮助我管理整个 Beta 测试流程和用户的工具。我正在寻找的功能是:

  • 免费的
  • Web 界面 - 让 beta 测试人员可以轻松访问
  • 易于配置 - 不想为每个 beta 测试人员创建登录名/凭证来使用工具
  • 必须能够提交问题/错误,以便我可以修复它们并更新错误(本质上是一个简单的票务系统)
  • 公开关于他们遇到的问题的评论/线程
  • 电子邮件警报会很好

有谁知道可以完成的工具这?

如果您之前有管理 Web 应用程序的一组 Beta 测试人员的经验,我将非常感谢任何提示或评论。

干杯,

Forgive me if this is in the wrong place, but I figured a few coders might have some thoughts on beta testing their code.

I have written a web application that I am going to beta test with a small audience (10-20), and will eventually develop an application for the iOS platform.

What I am looking for is a tool that will help me manage the entire beta testing process and users. The features I am looking for are:

  • Free
  • Web interface - to give easy access to beta testers
  • Easily configurable - dont want to have to create logins/credentials for each beta tester to use tool
  • Must be able to submit issues/bugs so that I may fix them and update bug (essentially a simple ticketing system)
  • Public comments/threads on issues they have come across
  • Email alerts would be nice

Does anyone know of a tool that will accomplish this?

If you have any prior experience managing a set of beta testers for a web application I'd greatly appreciate any tips or comments.

Cheers,

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

嘿哥们儿 2024-10-01 08:03:36

好吧,我对此没有具体的工具推荐,但根据我的经验,我发现自己实现这些东西是最简单的。

  • 很容易将反馈表放入您的应用程序中隐藏的某个地方,然后在测试期间链接到它。
  • 对于登录等,我只使用一个简单的注册代码系统(带有一个简单的管理 UI,用于添加更多注册代码)
  • 错误跟踪...根据您的受众,他们可能不会自己输入错误,因此请使用反馈表。如果您的受众是开发人员,那么您只需将他们指向您的 bugtracker,或者让他们向您发送电子邮件,您就可以输入它们 - 10-20 人并不是很多 bug 报告
  • 这种方法在金钱意义上是“免费”的: )

只是我的方法,有时在一个晚上把这些东西搞得非常粗糙是值得的,而不是设置/管理一个仅在测试期间使用的单独工具。当您的测试版结束时,通过这种方式,您只需删除相关代码(或者更好的是,重新调整它的用途,以便为博主或您在会议等场合遇到的人提供免费帐户)。

Well, I don't have a specific tool recommendation for this, but in my experience I've found it easiest to just implement this stuff myself.

  • Easy enough to throw a feedback form into your app hidden somewhere and just link to it during the beta.
  • For logins and such I just use a simple signup code system (with a simple admin UI for adding more signup codes)
  • Bug tracking... depending on your audience they probably wont be entering bugs themselves, so use the feedback form for this. If your audience is developers then you can simply point them at your bugtracker or just have them email you and you can enter them -- 10-20 people isn't a lot of bug reports
  • This approach is 'free' in the monetary sense :)

Just my approach, sometimes it's worth it to just bang out this stuff really rough in an evening rather than setting up/managing a separate tool which you'll only be using during the beta. When your beta is over, this way, you just delete the related code (or better, re-purpose it to facilitate free accounts for bloggers or people you meet at conferences and stuff).

雅心素梦 2024-10-01 08:03:36

经过更多研究后,我发现到目前为止我喜欢 Beta Easy。如果您有建议,我仍然想听听。

它仍然要求每个用户进行额外的登录,这有点烦人,但它为我提供了我在干净的界面中寻找的所有其他功能。

此处还提供了我在维基百科上发现的客户反馈管理工具列表。

After some more research I have found that I like Beta Easy so far. I'd still like to hear suggestions if you have them.

It still requires each user to have an extra login, which is kind of annoying, but it gives me all of the other features I'm looking for in a clean interface.

There's also a list of Customer Feedback Management tools I came across on Wikipedia here.

眉目亦如画i 2024-10-01 08:03:36

http://www.mantisbt.org/

我以前没有运行过这个,但我用过它可能会满足您的需求。

http://www.mantisbt.org/

I haven't run this before, but I've used it and it may suit your needs.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文