describe.feature

Info

Parent directory

isshub/domain/contexts/code_repository/entities/namespace/features/

Last update

Modified — 2020-10-06 17:30:45 +0200

Previous path

isshub/domain/contexts/core/entities/namespace/features/describe.feature

Last source

Feature: Describing a namespace

    Scenario: A namespace has an identifier
        Given a namespace
        Then it must have a field named identifier

    Scenario: A namespace identifier is a uuid
        Given a namespace
        Then its identifier must be a uuid

    Scenario: A namespace identifier is mandatory
        Given a namespace
        Then its identifier is mandatory

    Scenario: A namespace identifier cannot be changed
        Given a namespace
        Then its identifier cannot be changed

    Scenario: A namespace has a name
        Given a namespace
        Then it must have a field named name

    Scenario: A namespace name is a string
        Given a namespace
        Then its name must be a string

    Scenario: A namespace name is mandatory
        Given a namespace
        Then its name is mandatory

    Scenario: A namespace has a description
        Given a namespace
        Then it must have a field named description

    Scenario: A namespace description is a string
        Given a namespace
        Then its description must be a string

    Scenario: A namespace description is optional
        Given a namespace
        Then its description is optional

    Scenario: A namespace has a namespace
        Given a namespace
        Then it must have a field named namespace

    Scenario: A namespace namespace is a namespace
        Given a namespace
        Then its namespace must be a namespace

    Scenario: A namespace namespace is optional
        Given a namespace
        Then its namespace is optional

    Scenario: A namespace has a kind
        Given a namespace
        Then it must have a field named kind

    Scenario: A namespace kind is a NamespaceKind
        Given a namespace
        Then its kind must be a NamespaceKind

    Scenario: A namespace kind is mandatory
        Given a namespace
        Then its kind is mandatory

    Scenario: A namespace cannot be contained in itself
        Given a namespace
        Then its namespace cannot be itself

    Scenario: A namespace namespace cannot be in a loop
        Given a namespace
        And a second namespace
        And a third namespace
        Then we cannot create a relationships loop with these namespaces

Changes

feat(repository): Add domain repositories

Commit

Hash

27f013e2a3722926a9bbe300a77a493604f0993c

Date

2020-10-06 17:30:45 +0200

Type

Modified

Stats

+40 -40

@@ -1,75 +1,75 @@
-Feature: Describing a Namespace
+Feature: Describing a namespace

-    Scenario: A Namespace has an identifier
-        Given a Namespace
+    Scenario: A namespace has an identifier
+        Given a namespace
         Then it must have a field named identifier

-    Scenario: A Namespace identifier is a uuid
-        Given a Namespace
+    Scenario: A namespace identifier is a uuid
+        Given a namespace
         Then its identifier must be a uuid

-    Scenario: A Namespace identifier is mandatory
-        Given a Namespace
+    Scenario: A namespace identifier is mandatory
+        Given a namespace
         Then its identifier is mandatory

-    Scenario: A Namespace identifier cannot be changed
-        Given a Namespace
+    Scenario: A namespace identifier cannot be changed
+        Given a namespace
         Then its identifier cannot be changed

-    Scenario: A Namespace has a name
-        Given a Namespace
+    Scenario: A namespace has a name
+        Given a namespace
         Then it must have a field named name

-    Scenario: A Namespace name is a string
-        Given a Namespace
+    Scenario: A namespace name is a string
+        Given a namespace
         Then its name must be a string

-    Scenario: A Namespace name is mandatory
-        Given a Namespace
+    Scenario: A namespace name is mandatory
+        Given a namespace
         Then its name is mandatory

-    Scenario: A Namespace has a description
-        Given a Namespace
+    Scenario: A namespace has a description
+        Given a namespace
         Then it must have a field named description

-    Scenario: A Namespace description is a string
-        Given a Namespace
+    Scenario: A namespace description is a string
+        Given a namespace
         Then its description must be a string

-    Scenario: A Namespace description is optional
-        Given a Namespace
+    Scenario: A namespace description is optional
+        Given a namespace
         Then its description is optional

-    Scenario: A Namespace has a namespace
-        Given a Namespace
+    Scenario: A namespace has a namespace
+        Given a namespace
         Then it must have a field named namespace

-    Scenario: A Namespace namespace is a Namespace
-        Given a Namespace
-        Then its namespace must be a Namespace
+    Scenario: A namespace namespace is a namespace
+        Given a namespace
+        Then its namespace must be a namespace

-    Scenario: A Namespace namespace is optional
-        Given a Namespace
+    Scenario: A namespace namespace is optional
+        Given a namespace
         Then its namespace is optional

-    Scenario: A Namespace has a kind
-        Given a Namespace
+    Scenario: A namespace has a kind
+        Given a namespace
         Then it must have a field named kind

-    Scenario: A Namespace kind is a NamespaceKind
-        Given a Namespace
+    Scenario: A namespace kind is a NamespaceKind
+        Given a namespace
         Then its kind must be a NamespaceKind

-    Scenario: A Namespace kind is mandatory
-        Given a Namespace
+    Scenario: A namespace kind is mandatory
+        Given a namespace
         Then its kind is mandatory

-    Scenario: A Namespace cannot be contained in itself
-        Given a Namespace
+    Scenario: A namespace cannot be contained in itself
+        Given a namespace
         Then its namespace cannot be itself

-    Scenario: A Namespace namespace cannot be in a loop
-        Given a Namespace
-        And a second Namespace
-        And a third Namespace
+    Scenario: A namespace namespace cannot be in a loop
+        Given a namespace
+        And a second namespace
+        And a third namespace
         Then we cannot create a relationships loop with these namespaces

fix(entity): id changed from int to uuid4, renamed to identifier

Commit

Hash

79f704bde4575a9ddeb623d67d8965a62138adc9

Date

2020-10-05 10:51:49 +0200

Type

Modified

Stats

+8 -8

@@ -1,20 +1,20 @@
 Feature: Describing a Namespace

-    Scenario: A Namespace has an id
+    Scenario: A Namespace has an identifier
         Given a Namespace
-        Then it must have a field named id
+        Then it must have a field named identifier

-    Scenario: A Namespace id is a positive integer
+    Scenario: A Namespace identifier is a uuid
         Given a Namespace
-        Then its id must be a positive integer
+        Then its identifier must be a uuid

-    Scenario: A Namespace id is mandatory
+    Scenario: A Namespace identifier is mandatory
         Given a Namespace
-        Then its id is mandatory
+        Then its identifier is mandatory

-    Scenario: A Namespace id cannot be changed
+    Scenario: A Namespace identifier cannot be changed
         Given a Namespace
-        Then its id cannot be changed
+        Then its identifier cannot be changed

     Scenario: A Namespace has a name
         Given a Namespace

fix(entities): Entities id field are frozen once set

Commit

Hash

ef8edc20b6a674bfc98c79028684279bcc9ed324

Date

2020-09-27 09:56:59 +0200

Type

Modified

Stats

+4 -0

@@ -12,6 +12,10 @@ Feature: Describing a Namespace
         Given a Namespace
         Then its id is mandatory

+    Scenario: A Namespace id cannot be changed
+        Given a Namespace
+        Then its id cannot be changed
+
     Scenario: A Namespace has a name
         Given a Namespace
         Then it must have a field named name

fix(namespace): Namespaces relationships should not create a loop

Commit

Hash

afeb5f86809b05cf3ef131a59de1ed9235d59a8d

Date

2020-09-26 22:38:26 +0200

Type

Modified

Stats

+10 -0

@@ -59,3 +59,13 @@ Feature: Describing a Namespace
     Scenario: A Namespace kind is mandatory
         Given a Namespace
         Then its kind is mandatory
+
+    Scenario: A Namespace cannot be contained in itself
+        Given a Namespace
+        Then its namespace cannot be itself
+
+    Scenario: A Namespace namespace cannot be in a loop
+        Given a Namespace
+        And a second Namespace
+        And a third Namespace
+        Then we cannot create a relationships loop with these namespaces

fix(bdd): Rename “can/cannot be none” describing scenarios

Commit

Hash

cf1ea754ee276b16ddce53692a59174b2b583369

Date

2020-09-26 17:13:51 +0200

Type

Modified

Stats

+10 -10

@@ -8,9 +8,9 @@ Feature: Describing a Namespace
         Given a Namespace
         Then its id must be a positive integer

-    Scenario: A Namespace id cannot be None
+    Scenario: A Namespace id is mandatory
         Given a Namespace
-        Then its id cannot be None
+        Then its id is mandatory

     Scenario: A Namespace has a name
         Given a Namespace
@@ -20,9 +20,9 @@ Feature: Describing a Namespace
         Given a Namespace
         Then its name must be a string

-    Scenario: A Namespace name cannot be None
+    Scenario: A Namespace name is mandatory
         Given a Namespace
-        Then its name cannot be None
+        Then its name is mandatory

     Scenario: A Namespace has a description
         Given a Namespace
@@ -32,9 +32,9 @@ Feature: Describing a Namespace
         Given a Namespace
         Then its description must be a string

-    Scenario: A Namespace description can be None
+    Scenario: A Namespace description is optional
         Given a Namespace
-        Then its description can be None
+        Then its description is optional

     Scenario: A Namespace has a namespace
         Given a Namespace
@@ -44,9 +44,9 @@ Feature: Describing a Namespace
         Given a Namespace
         Then its namespace must be a Namespace

-    Scenario: A Namespace namespace can be None
+    Scenario: A Namespace namespace is optional
         Given a Namespace
-        Then its namespace can be None
+        Then its namespace is optional

     Scenario: A Namespace has a kind
         Given a Namespace
@@ -56,6 +56,6 @@ Feature: Describing a Namespace
         Given a Namespace
         Then its kind must be a NamespaceKind

-    Scenario: A Namespace kind cannot be None
+    Scenario: A Namespace kind is mandatory
         Given a Namespace
-        Then its kind cannot be None
+        Then its kind is mandatory

refactor(core): Rename core domain context to code_repository

Commit

Hash

07e279b370c0924f2b2cf32aea016b307001dfa0

Date

2019-08-15 23:31:33 +0200

Type

Renamed

Old path

isshub/domain/contexts/core/entities/namespace/features/describe.feature

Stats

+0 -0