Suggestion: Beta-testing of future Wealth-Lab .NET versions
Author: Wall
Creation Date: 9/25/2009 10:14 AM
profile picture

Wall

#1
I was looking forward to start using WLab .NET from v5.5 onwards but have again been disheartened by the bug reports so early after its release. Perhaps the developers of the software may wish to consider limited beta-testing the product prior to its release? If not for all releases, atleast for the 'major' ones?

The beta testers may be chosen randomly from a pool, or invited to participate based on their demonstrated expertise, or perhaps a combination of the two (a few expert users plus a few randomly chosen ones). While perhaps no software is completely bug-free, this beta-testing should help to detect the bugs that are easily caught (the more insidious bugs would likely surface later).

I make this post to invite user comments. I have no malice towards the developers.
profile picture

Cone

#2
While I agree with you that it would be highly beneficial, it's a waste of time to consider it. Due to legal constraints, Fidelity isn't going to release beta software for trading.
profile picture

Eugene

#3
Bugs are inevitable. Every software more complex than "Hello world" has bugs.
profile picture

Cone

#4
For sure the beta test idea is valid. The more eyes looking at app, the more bugs you're likely to find. But even though there are known bugs, at some point you have to draw a line to get a release out. For example, we're aware that an intermittent problem with Auto-Stage/Place persists from at least 5.3. But despite a multi-month effort, only 1 of at least 2 contributors to the problem could be isolated and resolved for 5.5. It could take months to finish isolating the problem (which the developers simply cannot duplicate), meanwhile, 5.5 was release which added several nice enhancements and fixed several known problems.
profile picture

Wall

#5
The beta-testing, if implemented, doesn't necessarily have to be extensive, just a limited one, with the intent that the easy bugs are, well, easily identified and, perhaps, just as easily fixed. That's why I had written:
QUOTE:
...may wish to consider limited beta-testing the product prior to its release?


If this beta-testing is done mid-way during the development of the next version, then it shouldn't significantly impact its release date.

Cone, you wrote:
QUOTE:
Due to legal constraints, Fidelity isn't going to release beta software for trading.
Trading would have to be disabled for beta-testing but (almost) all other aspects of the software would need to kept, such as Scans, Alerts, Real-time charting, and so on.

I know change is hard, but perhaps this beta-testing idea can be brought up in the next brainstorming session you guys have? To emphasize, limited beta-testing of a limited number of releases. Even the world's largest software company - Microsoft - employs beta-testing for its products destined for the general public.
profile picture

Cone

#6
It's already been brought up and shot down.
profile picture

Wall

#7
The idea can still be brought up again.

As a famous poet once wrote: If at first you don't succeed, try, try, try again.
profile picture

Cone

#8
Yes, please do!
profile picture

Wall

#9
Cone, I am doing my part by making some noise about it in the forum. If I happen to go a Traders Expo and see Glitch or VK, I will mention it to them (other users can do so, too). Unfortunately, other than that there's little else I can do.
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).