Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
TS-0019
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Specifications
Technical Specifications
TS-0019
Commits
013ae29f
Commit
013ae29f
authored
5 months ago
by
Miguel Angel Reina Ortega
Browse files
Options
Downloads
Patches
Plain Diff
Update file TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
parent
1b3ce83c
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!34
TDE-2024-0007_TS-0019-ATS_v4.2.0_baseline
Pipeline
#1680
passed
5 months ago
Stage: generation
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
+6
-6
6 additions, 6 deletions
...Test_Suite_&_implementation_eXtra_Information_for_Test.md
with
6 additions
and
6 deletions
TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
+
6
−
6
View file @
013ae29f
...
...
@@ -10,12 +10,12 @@
|
**Specification**
|
+:================+:=============================================+
|Document Number |oneM2M-TS-0019-V-4.2.0 |
+
:
----------------+
:
---------------------------------------------+
+
-
----------------+
-
---------------------------------------------+
|Document Name: |Abstract Test Suite and Implementation |
| |eXtra Information for Test |
+
:
----------------+:---------------------------------------------+
+
-
----------------+:---------------------------------------------+
|Date: |2024 March 1 |
+
:
----------------+
:
---------------------------------------------+
+
-
----------------+
-
---------------------------------------------+
|Abstract: |Abstract Test Suite and Implementation eXtra |
| |Information for Test consists of: |
| | |
...
...
@@ -26,7 +26,7 @@
| | naming conventions, code documentation, test|
| | case structure. |
| |- IXIT proforma; |
+
:
---------------------------------------------------------------+
+
-
---------------------------------------------------------------+
|Template Version:23 February 2015 (Do not modify) |
+----------------------------------------------------------------+
...
...
@@ -501,10 +501,10 @@ The rules for defining UtTrigger and UtTriggerAck primitives are:
+:================================+:==========================+:==============================================+
|OK |2000 |The SUT receives successfully the triggering |
| | |message from Test System |
+
:
--------------------------------+
:
--------------------------+
:
----------------------------------------------+
+
-
--------------------------------+
-
--------------------------+
-
----------------------------------------------+
|BAD
\_
REQUEST |4000 |The SUT does not interpret correctly the |
| | |UtTrigger primitive |
+
:
------------------------------------------------------------------------------------------------------------+
+
-
------------------------------------------------------------------------------------------------------------+
|NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |
+---------------------------------+---------------------------+-----------------------------------------------+
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment