2022-11-25 07:07 PM - last edited yesterday by Aruzhan Ilaikova
Hello together,
Frequently I'm disappointed, when I tested new functions etc. and I get the response: "We don't change anything now, the development of this is finished."
So my part as beta tester seems mainly to be, to report bugs and to search how the exactly arise.
A much more effective way to contribute to improve the program was in my eyes, to be much earlier involved in the development of new functions, tools options and so on.
I think the question should be:
… is it possible to do with the new thing the actions properly, for wicht it was actually designed?
… or far back: with functions and options in existing tools, display-options and so on, are missing mostly?
… or still far back: what is part of your everyday work and there is yet no function in Archicad?
…
Yes, the last to questions are more 'before test phase' – but at least the first one was in my opinion a significant method to test effectiveness and practicality of a new program version.
2022-11-26 04:08 AM - edited 2022-11-26 04:09 AM
There appears to be a definite distinction between the development phase and the Beta testing phase along with bug reporting and if the new functions perform as required.
I have been involved in the Beta testing for another CAD software but I am not familiar with the Archicad process.
From what I know, others feel they were just doing bug reporting mainly.