Hey Ricardo,That's a solid points you're making. In fact, that's exactly how it's supposed to work. Currently there are some known issues concerning the code history in combination with branching and merging. We are working on a fix and we'll roll this out as soon as we can.Thanks for your suggestion!
Hi René, First of all, I'm glad to see that the unit test functionality is being used, especially in combination with mock data! You have a strong case there, showing the exact problem we have faced using unit tests with mock data, while developing 2020.1. The good news is, that this exact problem is already fixed in the 2020.1 development. This version will soon be released. I hope this answers your question.
Hi René, First of all, it's great that you're using unit tests! You're correct to point out that views shouldn't belong in data sets. The data used by the views should be stored in the underlying tables. Therefore, the views should be excluded from the table selection for data sets. Thanks for reporting this bug, we will fix this as soon as possible! With kind regards, Serhat Sahin
Hi Harm, This feature can be turned on by changing the user preferences configuration in the user table. User preferences configurationWhen you click on the look up button, you can see several predefined configurations. List of configurationsThese configurations show which actions will be recorded in the use log user action table. If the predefined configurations don't match the requirements, a custom configuration can be added. I hope this will answer your question.
Hi Marcel, As you describe it, it should work fine. So I'm wondering what the missing context is. If I understood you well, you are trying to do the following: Code: if @cursor_from_col_id = 'postal_code’ and @postal_code is not null begin set @postal_code = REPLACE(@postal_code, ' ', ''); end;Unit test parameters: INPUT: @cursor_from_col_id = postal_code INPUT: @postal_code = 1234 AB EXPECTED OUTPUT: @postal_code = 1234AB Result: Expected: success (@postal_code = 1234AB) Actual result: failed (@postal_code = 1234 AB) This situation should indeed be an expected success. Are you sure that there is nothing else altering the code, and that the default procedure code is executed on the database? I'll need to look into this case to figure out what causes the problem. It indeed seems like an easy unit test scenario. With kind regards, Serhat Sahin
Thanks for all replies. You've picked the right piece of code from the debug. Even the debug seems okay… Just to clarify, the double quotes are needed to execute the whole as a string (so double quotes will become a single quote), so you can ignore those and replace them with single quotes in SQL Server. The select statement is selecting the output parameters. The cursor_from_col_id parameter is an input parameter only, that's why it's excluded in the select statement. Could you check your private messages for me? I've sent you a message to help you in this matter and try to figure out what's wrong with this whole scenario.
Hi Marcel,That's a great suggestion as the next step in the requirements and design feature!In fact, we've even implemented this feature in the next platform release! For now I must ask you to be patient and enjoy this sneak peak:In the next release it will be possible to add effort (estimated, remaining and completed) to work.Estimated effort (hours) within work itemsIt will also be possible to add story points to requirements and sum the total remaining hours of linked work. T-shirt sizes are used for this example, but these values will be editable.Story points within requirementsThe total remaining hours and total story points will also be visible within the linked iteration. I hope the sneak peak gave you a clear idea of what's coming up and that the functionality is as expected.By implementing this step, we've added more awesome new ideas to our roadmap!I suggest you start improving your poker face With kind regards,Serhat Sahin
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.