94 lines
3.7 KiB
HCL
94 lines
3.7 KiB
HCL
At about other non-functional tests. Several NFR related tasks are in this release, hence this should also be tested
|
|
Related to performance assessment, not sure what the comment means. OH, I think it's about NFR in general, OK
|
|
|
|
Please add: «Testing in a multi-agent setup to ensure the correct functioning of Simpl-Open in a more realistic setup»
|
|
Yup
|
|
|
|
See my comments in section 1.2
|
|
Yup
|
|
|
|
What about the SAs ? These should also be added
|
|
SA - supporting activities. What jira stories are not part of a BP should be checked if they are part of any SA and list them as a separate table.
|
|
|
|
This is not related to BP12, but SA04
|
|
Will move it, but it was linked to an epic that has BP12 labels
|
|
|
|
SAxx and BPxx are the same as previous. Will be moved, but jira should also be updated.
|
|
|
|
The categorisation in this section is not properly done. You should introduce the SAs (see my earlier comment) and NFR to properly organise the tickets. I provided on some tickets how to categorise them, but please recheck all
|
|
Yes, as per earlier comment, we will add a new table for SAs.
|
|
|
|
These are related to SA04 (also 3 next ones)
|
|
Yes
|
|
|
|
-- the same for the others, covered in the table fixing activities
|
|
|
|
This is linked to BP12, so why is it mentioned here ?
|
|
Will check and fix
|
|
|
|
What you mention here are not the last releases
|
|
Will fix with the last release (Firenze)
|
|
|
|
+ installation test in a separated PSO environment
|
|
Yup
|
|
|
|
behaviour
|
|
Yup
|
|
|
|
What is meant by the PSO infrastructure services ?
|
|
To remove "PSO"
|
|
|
|
What is this PSO monitoring ?
|
|
To remove "PSO"
|
|
|
|
Please add tests for SA and NFRs that are in the scope
|
|
Yup
|
|
|
|
Adding specific checks relevant for multi-agent setup
|
|
Will update the text to mention it
|
|
|
|
Can you add the environment for each of these tests as now different environments are used ?
|
|
Will update each section with the used environment
|
|
|
|
This looks very limited, why not run all automated tests ?
|
|
IDK ?
|
|
|
|
Which deployment are you referring to ? The one done by SC1 or the one by PSO ?
|
|
As stated above, will update each section to mention the used environment.
|
|
|
|
And Supporting Activities
|
|
Yup
|
|
|
|
Besides the supporting activities, also some BPs are missing, e.g. BP02 and its subprocesses, BP03B, BP03C … This section is still like for MVP while many things were added
|
|
Will update the list of test cases
|
|
|
|
What about health checks ? What about configuration of dashboards, reports etc
|
|
Will update the list of test cases to include the ones left out of this document.
|
|
|
|
This is not a proper setup. You should have separated consumers and providers, each with their own common components. Also GA should be separated and have their own common components
|
|
Noted. We will update the plan to make sure agents do not share common components.
|
|
|
|
There are several tickets related to horizontal scaling and other NFR, where are these tested ? What about the multilinguism that is implemented in some components ? Is it tested ?
|
|
New sections will be added for the mentioned functionalities where applicable and the sections updated to include relevant testing activities.
|
|
|
|
Would it not be good to have one of the BAs or Architects to do this ? They have a better view on what is expected and probably can find things that might not be covered by test cases ...
|
|
IDK ?
|
|
|
|
And SAs
|
|
Yup
|
|
|
|
Should this not be updated now that SC1 is doing first a deployment to speed up the process ?
|
|
Will revise the list of tasks to explicitly be mapped on the correct flow.
|
|
|
|
See earlier comment, is this still aligned with the updated process ?
|
|
We will double check and update if necessary.
|
|
|
|
There is no weekly report anymore, please update everywhere
|
|
OK.
|
|
|
|
typo
|
|
Yup
|
|
|
|
Is this a statement for all environments or for this specific one ? Please provide clear explanations of the purpose of each environment
|
|
Will update the section to clearly explain the purpose of each environment.
|