Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When you have created / adjusted functionality and as a consequence also created a unit test, the functionality can be send to the review process. Also, you can see the (results of) the linked unit tests.At the moment, the unit test itself is not a part of the review process. To improve quality, I suggest to make unit tests be part of the review process.
As a reviewer I would like to be able to view all changes to the data model and accept them or reject them with comments. This is because I run into some cases where fellow developers have made some mistakes designing the data model. (for example, wrong use of keys, references etc). One can dispute that things like keys, names, etc would pop-up when you review the sub names and validations. But sometimes it checks all the boxes of the validations but still is not a data model where you as a reviewer can agree up-on. So I would like to see something like the Code review screen but then for data modelling. And maybe include in that screen the use of the on a detail screen sub names and show relevant validations.
As a developer, I want to be able to pass "dynamic" values to the UI while queries are running, to inform the user of activity. For example, when I have a default that requires, say, a template/script having 5 queries to run before it fills an input field, I want to indicate a percentage of "20%/40%/60%/80%/100% done" before the input field(s) get filled. Or, I want the field(s) that will be filled by the result of the SQL script to indicate activity (an hour glass, or 1-dot-2-dots-3-dots-1-dot-2-dots-3-dots, you get the idea, something like a spinner) in the input field as long as the default template/script gets executed, for long(er)-running scripts. The UI remains responsive and active during execution of the SQL script(s), so the user experience would improve because of this.This idea is based on the case presented here:https://community.thinkwisesoftware.com/questions-conversations-78/progress-or-activity-indicator-for-automatically-filled-fields-3631
Once in a while a run a query to see unused indexes on applications I am working on. The query result shows (most of the time) that a lot of indexes are not used. The Software Factory automatically creates indexes for each reference. Since it takes time to maintain indexes (performance loss), I would like the ability to indicate that I do not want an index.For example,In the Reference, make available a checkbox “Create index” which is by default checked (same as current functionality). When you do not want the index the developer unchecks the box and the (smart) upgrade script will drop the index and not recreate it again.Unchecking the “Create index” checkbox (like unchecking the “Check integrity” checkbox) must be done with care, but when having this option, this could increase performance in certain cases.
The Software Factory offers the ability to set up automated testing via the unit test section. This will allows you to test if a specific error message is returned or whether an action is executed successfully.What would be a great enhancement in this, is to define a max duration time for you test.Sometimes, after a change, the action is still successful but will take quite a bit longer than before. If you were to release the version containing this change, the increased duration could lead to an issue.With the option of introducing a max duration per test, you could prevent these kind of issue from being released.
It seems like that the option 'Start empty with filter’ only affects subjects when showed as main screen.Would it be possible to let this work on detail screens as well?
Code that calls a function can be difficult to test if that function performs significant logic. I want to isolate the code we are testing from the logic buried in the functions that it calls. To create independent tests, you should be able to fix the output of some functions.For example when you have a task that confirms a sales order, you don’t want to unit-test the function that checks for a credit limit. The credit-limit check should just return ‘ok’.Another big advantage is that this will reduce the amount of mock data required to perform the unit test. In some cases you have to fill half a database in order to get a function to return a ‘true’ whilst not even testing that function.
It would be nice to have the possibility to show specific tasks on each row in a form list. Not all tasks, because it depends on the function of a task.
It would be nice if a task is executed over a multiline select in the grid, this selection is retained after the task has been executed. This way a 2nd task can be executed over the same selection.
In current version of TSF it is seems not to be possible to synchronize from TSF to IAM when the target DB credentials differ from the TSF Webservice credentials.Because of this, in case the credentials cannot be made equal creating a deployment package seems to be the only way to sync IAM, which is not desirable, because this is to much complicated. Especially in case of a making small changes, like a little adjustment in a roles, this cost to much time.I would expect a possibility to enter credentials before starting the sync process or save the credentials (securely) in the IAM Configuration. Or, have I missed something and is there already an easier way?
Currently the ‘Code reviews’ screen shows code reviews per control procedure. Templates within a control procedure can be changed by different developers. We would like to see every control procedure template as an individual code review item. This would allow a reviewer to approve or disapprove a single template. This will also allow you to see at a glance which templates must be reviewed without having to look in the tabpage 'Changes’.
From the screen ‘Code reviews’ it’s possible to approve and disapprove control procedures. When we accidentally set a control procedure ‘Approved’ there’s no way to undo it because the ‘Approve’ and ‘Disapprove’ tasks are disabled. It would be a nice feature to be able to ‘Disapprove’ an already approved control procedure.
However the source code generation step has never failed me, I sometimes wonder if it is doing something. I’d like to have a more verbose output of what it is actually doing and at what step the generation process is.Currently we only see this and just have to wait:It would be nice if we are able to see the smaller steps that are happening inside a specific step. The advantage is two-fold. It keeps you up to date and makes it visible if there are any steps that are running slowly.
By setting a different background color for templates that are in a certain state it will make it easier to focus only on those templates that need it.For instance think about templates that need some fixing, have or haven't changed since last review, have been reviewed and wait response of developer, alongside prefilters to make you focus on one or the other.This not only within the Review code section, but also within the Functionality (Control procedure and templates).
Importing/adding translations and validating translations are tasks that are sometimes attributed to specific persons in the project team that are not developers. This is especially likely to happen when a high number of languages and/or more exotic languages are to be supported.To better support this scenario a formalized translator user group (and underlying roles) in the Software Factory would be beneficial. Users that are part of such a group should have access to the “Translations” menu item and the tasks to generate and translate translation objects and the possibility to import/export translations without having the possibility to change the data-/gui model and functionality.
Unit tests are great way to test API's however, our API's have the declared parameter @error_msg. Because this is the same parameter as declared in the unit test code all of our API's get the same failed message for their unit test: This is probably a more common problem, because @error_msg is a widely used parameter. Can this parameter be changed to a more uncommon one, specific for unit testing probably?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.