• SONAR
  • Cakewalk Problem Reporter is a problem
2013/11/26 22:57:18
Splat
Hello
In regards to Cakewalk problem reporter:
http://www.cakewalk.com/s...act/problemreport.aspx
 
I appreciate steps to reproduce problems should be like this:
----------------------------------------------------------
STEPS to reproduce

1) Do blagh

2) Click blagh
3) Click blagh blagh


Expected

Blagh Happens


Actual


Blagh happened followed by a crash.

----------------------------------------------------------
 
I also appreciate that actually following steps at your end requires painful insertion of each step line by line into Visual Studio's Testing UI so you can write test cases, however please don't expect me to paste each step line by line for you.. this actually puts me off, and probably puts other end users off to be honest.

I just need to paste in my steps all in one go (I've already written them in notepad), if you need to paste it into your testing app line by line that's your job to be honest :)


BTW I always paste the steps into your results form :).
 
Thanks!
2013/11/26 23:54:53
brian brock
yeah it is a problem.  Also I feel that it should be incorporated into the forum somehow, so that when signed in the problem reporter remembers your serial number and other such things.  I understand the desire to ensure that problems are reported by people actually using the software, but I don't think it needs to be quite so complicated.
2013/11/27 00:05:17
icontakt
The email tech support system also has a problem. The auto reply email should contain the ticket number.
2013/11/27 00:49:19
Ryan Munnis [Cakewalk]
Alex, I've seen you hypothesize that we do this because we're importing test cases into VS before, but that's not the reason (honestly I'm not even sure how that would work). The reason was so people would provide steps and not type novellas :)

Since we added the steps box, most people provide steps. It's proven to be helpful. Wear my shoes for a week and you'll understand :)

It has nothing to do with scripts and everything to do with me and other staff not wanting to have to ask people for steps multiple times (essentially wasting more of their time). I know you don't bother putting steps into the steps box given it's annoying, but you provide good info anyway so it's really not a big deal.

I've noticed some compatibly issues with the form lately anyway, so it needs a redesign. We'll try to get to that soon.
2013/11/27 00:50:42
Ryan Munnis [Cakewalk]
Jlien X
The email tech support system also has a problem. The auto reply email should contain the ticket number.


+1

Also noted. :)
2013/11/27 02:29:06
Splat
Since we added the steps box, most people provide steps. It's proven to be helpful. Wear my shoes for a week and you'll understand :)
 
Actually I have. I did QA for about 5 years on another software product. Exactly the same scenario but this time I wasn't the customer... So I understand. I've also done test case automation hence my assumption here that this is what you are trying to do. Point is if you've got 20 steps its a bit of a nightmare pasting 20 steps into a webform...
 
...and yeah and I know when most people write bug reports, it's full of assumptions that you already know what is going on, that software is easy and quick to fix... and test, and it's a nightmare :)
 
Let's put it this way for people who haven't done this, if you work in software don't expect to go home 6pm every night, expect to wake up and work, and go to bed and work. Nature of the beast.
2013/11/27 07:01:59
cowboydan
I dont think that this is the way to apply for a NEW JOB ALEX

2013/11/27 07:05:15
Splat
CV attached :)
2013/11/27 07:08:47
cowboydan
Negative Applications are also applications I guess.
 
GO FOR IT !
2013/11/27 07:31:16
gswitz
I have absolutely no probs with the problem reporting system. For me, it's fast and easy.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account