IdeaIn essence, the idea is to expand the quality dashboard with a manual test scenario section, where users can see the number of test cases, successful test executions, combined with failed tests, and the number of open findings.ContextOver the past few releases, we've introduced the Manual Test Scenarios feature, allowing for the easy registration of test scenarios, which are now centrally available for the development team. The most recent update consolidates the registration of both these test scenarios and test executions into a single location within the Software Factory.Another improvement is the introduction of a dedicated Test Role. This enables key users or process owners to register their test scenarios and test executions within the Software Factory without being distracted by other functionalities.Now, what we're aiming for is to provide a quick overview of the testing progress, not only for the development team but also for the product owner and potentially steering comm
I would like the smoke tests to be added to the quality dashboard. This could be added in the 'test quality' section.Furthermore, in the same style and presentation as the other test types.
The overview of unit tests has already been enriched in recent releases with the fields 'Abort', 'Preparation' and 'Assertion'. In the same way, we want to see which unit tests use mock data. This way, you can see more quickly which unit tests fail in combination with mock data. This helps to predict the efforts a team will have to put into this mock data. Assuming that applications grow and data models change, more priority can be given to maintaining, keeping these data sets realistic.
We increasingly encourage to register the test scenarios they have in the SF under Manual Test Scenarios. Key users should also be able to do this. Both the registration of these scenarios and the execution of a test run. This also includes creating findings. There is actually no role for this yet. A test role. A role that only makes these test functionalities available. The situation is such that we have indicated that we will register the test scenarios in the SF. These are currently in an Excel file.Later, if Key-users are going to perform regression tests, for example, it would be appropriate if they could do this via the SF. Then all these test runs are registered. The wish is therefore to create a test role that can at least be used for the following components:Specification -> Manual Test Scenarios Quality -> Manual Tests
At Deployment -> creation -> tab unit tests you can find many unit tests. It would be nice if there could be a progress bar that at least informs the user of the progress.
Being able to make 1 unit test that can be connected to multiple objects. For examplethe unit test for a default that occurs in several places in the system in that form.
Filter objects to be selected on only the assigned assignments Further explanation:Unittest screen -> choice for default, And choice for object. I can still choose from all control procedures.
Validation that checks whether all control procedures have a unit test.It is not necessary to make unit tests part of the project for every project. Wish to make configurable to make validations on unmade unit tests.
Can a possibility be created to categorize unit tests. For example to group by module (calculation, financial). This will help to effectively check whether the quality of a module is still sufficient after adjustments.
Hi, In my applications that I've build so far in my training, i've struggle finding a way to change the format of dates shown in my pages. At the moment it's like this: mm/dd/yyyy But what I want is this: dd-mm-yyyy What is the proper way to achieve this?
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.