You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TSF/trustable/assertions/TA-BEHAVIOURS_CONTEXT.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,11 +49,10 @@ sufficient.
49
49
50
50
- List of Expectations
51
51
-**Answer**: The Expectations are provided via JLEX-01 and JLEX-02.
52
-
- Argument of sufficiency for break-down of expected behaviour for all
53
-
Expectations
54
-
-**Answer**: TODO: Create a new statement JLS-56 about sufficiency of break-down and reference JLEX-01 and JLEX-02.
52
+
- Argument of sufficiency for break-down of expected behaviour for all Expectations
53
+
-**Answer**: See JLS-56.
55
54
- Validation and verification of expected behaviour
56
-
-**Answer**: The validation and verification of expected behaviour is done via the evidence provided for all the statements below JLEX-01 and JLEX-02 in the trustable graph. TODO reference JLS-03.
55
+
-**Answer**: The validation and verification of expected behaviour is done via the evidence provided for all the statements below JLEX-01 and JLEX-02 in the trustable graph, in addition to JLS-03.
57
56
58
57
59
58
**Confidence scoring**
@@ -71,7 +70,7 @@ and that the resulting system and tests are validated by appropriate strategies.
71
70
- Could some participants have incentives to manipulate information?
72
71
-**Answer**: We cannot imagine any incentive to manipulate information.
73
72
- Could there be whole categories of Expectations still undiscovered?
74
-
-**Answer**: It is currently unlikely that there are whole categories of Expectations still undiscovered. TODO mention SME reviews increase confidence
73
+
-**Answer**: It is currently unlikely that there are whole categories of Expectations still undiscovered.
75
74
- Can we identify Expectations that have been understood but not specified?
76
75
-**Answer**: There are currently no Expectations that have been understood but not specified.
77
76
- Can we identify some new Expectations, right now?
@@ -85,6 +84,6 @@ and that the resulting system and tests are validated by appropriate strategies.
85
84
- Are there any Expectations where we believe more coverage would help?
86
85
-**Answer**: No, the coverage is already on a high level and no further gains are expected by further increasing the coverage.
87
86
- How do dependencies affect Expectations, and are their properties verifiable?
88
-
-**Answer**: The nlohmann/json library does not have external dependencies, so that there are none that could possibly affect the Expectations. TODO say that this doesnt apply to testing
87
+
-**Answer**: The nlohmann/json library does not have any external dependencies apart from the testing pipeline, so there are no dependencies that could possibly affect the Expectations.
89
88
- Are input analysis findings from components, tools, and data considered in relation to Expectations?
90
-
-**Answer**: TODO ask in libera chat or look through TA-Behaviours
89
+
-**Answer**: For components, there is no input analysis as the nlohmann/json library has no external components (see JLS-34). For Tools, a tool assessment is provided via JLS-50. In addition, the only data provided to the nlohmann/json library is the input data when using the libraries' functionality.
0 commit comments