Develop Use Case Test cases that actually work

fciani

One of the most frustrating things when working with any software application is when it doesn't behave as expected. Sometimes these issues are nuances rarely seen, but more often than not it is simply bad coding and bad software review.

With the recent update, I can no longer change the Report Title. It's a new year. I have last year's report title (Data 2022). I now want to change it to (Data 2023). Can't. This functionality worked before. [And I think many users would agree - We do NOT want to be told 'The work around for this is...' That normally means we ain't fixing it - ever.]

I've also noticed that some changes cannot be made to a current transaction. So, if I made a data entry and want to change the transaction, some fields won't update.

I think most of these issues could be avoided if the proper Use Cases were developed. The testing of software changes would then be much more comprehensive and these issues would be corrected BEFORE the software gets deployed.

Rocket J Squirrel

fciani said:

With the recent update, I can no longer change the Report Title. It's a new year. I have last year's report title (Data 2022). I now want to change it to (Data 2023). Can't. This functionality worked before.

I can change report titles in QWin R46.9.

If you are using reports which live in Quicken's Tool Bar, those apparently are copies of - not pointers to - the reports in Saved Reports. If you delete the Tool Bar report and reinstall it, you should get the new title from your saved report.

If that's not your problem, please explain further.