Mock example

.circleci/config.yml

@@ -0,0 +1,48 @@
+version: 2.1
+
+jobs:
+  deployment-and-api-tests:
+    machine:
+      image: ubuntu-2004:202010-01
+    steps:
+      - checkout
+      - run:
+          name: 'Test Scheduler Build Block API'
+          command: 'echo testing all examples in /examples against test suite in /test'
+      - run:
+          name: Deploy Mock APP for Scheduler BB API and PyTest Containers
+          command: cd examples/mock && docker-compose up --build -d
+      - run:
+          name: Check Status of Mock App and API Testing Containers
+          command: docker ps
+      - run:
+          name: Testing Scheduler BB API
+          command: 'echo testing using containers'
+      - run:
+          name: Check Status of Testing Containers are Deployed
+          command: docker ps
+      - run:
+          name: Run Pytest tests against Register BB Mock to generate test result in Junit XML Format for Test Summary
+          command: docker exec -i pytest pytest -k smoke -s --junit-xml=/tmp/test-results/pytest-results.xml || true
+      - run:
+          name: Run cucumber tests against Register BB Mock to generate test result in JSON Format
+          command: docker  exec -i pytest  pytest -k smoke  -s --json-report --json-report-indent=4 --json-report-file=/tmp/test-results/smoke_testing_report.json || true
+      - run:
+          name: Copy test results to host machine
+          command: docker cp pytest:/tmp/test-results /tmp
+      - store_test_results:
+          path: /tmp/test-results
+          prefix: junit-
+          destination: /test-results/
+      - store_artifacts:
+          path: /tmp/test-results
+
+workflows:
+  deployment-and-api-tests:
+    jobs:
+      - deployment-and-api-tests:
+          filters:
+            branches:
+              only:
+                - mock_example
+

examples/mock/docker-compose.yml

@@ -0,0 +1,27 @@
+version: "3"
+services:
+  mockoon:
+    image: mockoon/cli:latest
+    command: -d /data # this is where the change takes place
+    container_name: myapi
+    ports:
+      - "3000:3000"
+    networks:
+      demo:
+    volumes:
+      - type: bind
+        source: ../../api/Scheduler_OpenAPI_17042023_V3.json    
+        target: /data 
+  pytest:
+   build:
+     context: ../../test/.
+   container_name: pytest
+   tty: true
+   stdin_open: true
+   networks:
+      demo:
+
+
+networks:
+      demo:
+

test/Dockerfile

@@ -0,0 +1,8 @@
+#FROM joyzoursky/python-chromedriver:latest
+#FROM qnib/pytest  
+FROM python:3.8
+COPY requirnments.txt requirnments.txt
+RUN pip3 install -r requirnments.txt
+COPY .  /test
+WORKDIR /test/
+CMD /bin/bash  

test/features/createaffiliationnew.feature

@@ -0,0 +1,44 @@
+@method=POST @endpoint=/affiliation/new/
+Feature: Create a new affiliation of Scheduler API
+
+Gherkin feature files for GovStack Scheduler services
+
+@smoke  
+Scenario: Create a new affiliation for Scheduler API Smoke Test   
+
+Given the requestor Id is "healthngo1" with role as "healthworker" to create a new affiliation
+When a POST request for an endpoint /affiliation/new/ is triggered to create new affiliation for scheduler block      
+Then the result should return affiliation Id as "1" for smoke testing
+And response code of POST request is "200" for smoke testing 
+
+
+
+@unit @happyregression  
+Scenario Outline: Create a new affiliation for Scheduler API Unit and Regression Happy Testing
+
+Given the requestor id is "<requestor_id>" with role as "<requestor_role>" to create an affiliation with its details "<resource_id>" "<entity_id>" for resource of category "<resource_category>" for a schedule on "<day_of_week>" from "<start_time>" to "<end_time>"
+When a POST request for an endpoint /affiliation/new/ is triggered to create new affiliation for scheduler block
+Then the result should return affiliation details like "<affiliation_id>" and "<affiliation_name>" for requested affiliation
+And response code of POST request is "200"
+
+Examples: 
+  | requestor_id | requestor_role | resource_id | entity_id | resource_category | day_of_week | start_time | end_time | affiliation_name | affiliation_id |
+  | healthngo1   | healthworker   | 12345       | 67890     | physician         | monday      | 09:00:00   | 17:00:00 | xyz hospital     | 1              |
+
+
+@unit @Negativeregression  
+Scenario Outline: Create a new affiliation for Scheduler API Unit and Regression Negative Testing
+
+Given the invalid inputs for the requestor id is "<requestor_id>" with role as "<requestor_role>" to create an affiliation with its details "<resource_id>" "<entity_id>" for resource of category "<resource_category>" for a schedule on "<day_of_week>" from "<start_time>" to "<end_time>"
+When a POST request for an endpoint /affiliation/new/ is triggered to create new affiliation for scheduler block
+Then response code of negative testing POST request for invalid data is "<status_code>"
+
+
+
+Examples:
+  | requestor_id | requestor_role | resource_id | entity_id | resource_category | day_of_week | start_time | end_time | status_code |
+  | healthngo1   | healthworker   | 12345       | 67890     | physician         | monday      | 09:00:00   | 17:00:00 | 400         |
+  | healthngo1   | healthworker   | 12345       | 67890     | physician         | monday      | 17:00:00   | 09:00:00 | 403         |
+  | healthngo1   | healthworker   | resource    | 67890     | nurse             | monday      | 17:00:00   | 09:00:00 | 404         |
+
+

test/features/createalertschedulenew.feature

@@ -0,0 +1,43 @@
+@method=POST  @endpoint=/alert_schedule/new/
+Feature: Create a new Alert Schedule for Management of Scheduler API
+
+Gherkin feature files for GovStack Scheduler services
+
+@smoke  
+Scenario: Create a new Alert Schedule for Management of Scheduler API Smoke Test   
+
+Given the requestor Id is "healthngo1" with role as "healthworker" to create a new alert schedule
+When a POST request for an endpoint /alert_schedule/new/ is triggered to create new alert schedule for scheduler block      
+Then the result should return alert schedule Id as "1" for smoke testing
+And response code of POST request is "200" for smoke testing 
+
+
+
+@unit @happyregression  
+Scenario Outline: Create a new Alert Schedule for Management of Scheduler API Unit and Regression Happy Testing
+
+Given the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a new alert schedule with event "<event_id>" for "<target_category>" with "<message_id>" within a "<alert_datetime>"
+When a POST request for an endpoint /alert_schedule/new/ is triggered to create new alert schedule for scheduler block
+Then the result should return alert details like "<alert_schedule_name>" and "<alert_schedule_id>" for requested schedule
+And response code of POST request is "200"
+
+Examples: 
+  | requestor_id | requestor_role | event_id | target_category | message_id | alert_datetime      | alert_schedule_name | alert_schedule_id |
+  | healthngo1   | healthworker   | 12345    | subscriber      | 1          | 2018-02-15T09:00:00 | xyz hospital        | 1                 |
+
+
+@unit @Negativeregression  
+Scenario Outline: Create a new Alert Schedule for Management of Scheduler API Unit and Regression Negative Testing
+
+Given the invalid inputs for the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a new alert schedule with event "<event_id>" for "<target_category>" with "<message_id>" within a "<alert_datetime>"
+When a POST request for an endpoint /alert_schedule/new/ is triggered to create new alert schedule for scheduler block
+Then response code of negative testing POST request for invalid data is "<status_code>"
+
+
+
+Examples:
+  | requestor_id | requestor_role | event_id | target_category | message_id | alert_datetime     |  status_code |
+  | healthngo1   | healthworker   | 12345    | subscriber      | 1          | 2018-02-15T09:00:00|  400         |
+  | healthngo1   | healthworker   | 12345    | subscriber      | 1          | 2018-02-15T09:00:00|  403         |
+  | healthngo1   | healthworker   |12345     | subscriber      | 1          | 2018-02-15T09:00:00|  404         |
+

test/features/createappointmentnew.feature

@@ -0,0 +1,42 @@
+@method=POST  @endpoint=/appointment/new/
+Feature: Create a new appointment of Scheduler API
+
+Gherkin feature files for GovStack Scheduler services
+
+@smoke  
+Scenario: Create a new appointment of Scheduler API Smoke Test   
+
+Given the requestor Id is "healthngo1" with role as "healthworker" to create a new appointment
+When a POST request for an endpoint /appointment/new/ is triggered to create new appointment for scheduler block      
+Then the result should return appointment Id as "67890" for smoke testing
+And response code of POST request is "200" for smoke testing 
+
+
+
+@unit @happyregression  
+Scenario Outline: Create a new appointment of Scheduler API Unit and Regression Happy Testing
+
+Given the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a new appointment for an entity with "<entity_id>" and "<entity_type>" for participant of "<participant_type>" "<participant_id>" and "<participant_entity_id>" for a time period "<From>" till "<To>" with deadline "<deadline>"
+When a POST request for an endpoint /appointment/new/ is triggered to create new appointment for scheduler block
+Then the result should return appointment details like "<appointment_id>" and "<appointment_name>" for requested appointment
+And response code of POST request is "200"
+
+Examples: 
+  | requestor_id | requestor_role | entity_id | entity_type         | participant_type | participant_id | participant_entity_id | From                | To                  | deadline            | appointment_name   | appointment_id |
+  | healthngo1   | healthworker   | 1         | doctor_consultation | subscriber       | 12345          | 67890                 | 2018-02-15T11:00:00 | 2018-02-15T11:30:00 | 2018-02-15T11:10:00 | doctorconsultation | 1              |
+
+
+@unit @Negativeregression  
+Scenario Outline: Create a new appointment of Scheduler API Unit and Regression Negative Testing
+
+Given the invalid inputs for the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a new appointment for an entity with "<entity_id>" and "<entity_type>" for participant of "<participant_type>" "<participant_id>" and "<participant_entity_id>" for a time period "<From>" till "<To>" with deadline "<deadline>"
+When a POST request for an endpoint /appointment/new/ is triggered to create new appointment for scheduler block
+Then response code of negative testing POST request for invalid data is "<status_code>"
+
+
+
+Examples:
+ | requestor_id | requestor_role | entity_id | entity_type         | participant_type | participant_id | participant_entity_id | From                | To                  | deadline            | status_code |
+ | healthngo1   | healthworker   | 1         | doctor_consultation | subscriber       | 12345          | 67890                 | 2018-02-15T11:00:00 | 2018-03-15T11:30:00 | 2018-02-15T11:10:00 | 400         |
+ | healthngo1   | healthworker   | 1         | doctor_consultation | subscriber       | 12345          | 67890                 | 2018-02-15T11:45:00 | 2018-02-15T11:30:00 | 2018-02-15T11:10:00 | 403         |
+ | healthngo1   | healthworker   | 1         | doctor_consultation | subscriber       | 12345          | 67890                 | 2018-02-15T11:00:00 | 2018-07-15T11:30:00 | 2018-02-15T11:10:00 | 404         |

test/features/createlognew.feature

@@ -0,0 +1,42 @@
+@method=POST  @endpoint=/log/new/
+Feature: Create a new Log of Scheduler API
+
+Gherkin feature files for GovStack Scheduler services
+
+@smoke  
+Scenario: Create a new Log of Scheduler API Smoke Test   
+
+Given the requestor Id is "healthngo1" with role as "healthworker" to create a new log
+When a POST request for an endpoint /log/new/ is triggered to create new log for scheduler block      
+Then the result should return log Id as "1" for smoke testing
+And response code of POST request is "200" for smoke testing 
+
+
+
+@unit @happyregression  
+Scenario Outline: Create a new Log of Scheduler API Unit and Regression Happy Testing
+
+Given the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a log for role "<logger_role>" with its Id "<logger_id>" "<entity_id>" for category "<log_category>" from time period of "<datetime>" with data as "<log_data>"
+When a POST request for an endpoint /log/new/ is triggered to create new log for scheduler block
+Then the result should return log details like "<log_name>" and "<log_id>" for requested log
+And response code of POST request is "200"
+
+Examples: 
+  | requestor_id | requestor_role | logger_role | logger_id | entity_id | log_category | datetime            | log_data                                                       | log_name     | log_id |
+  | healthngo1   | healthworker   | resource    | 1         | 67890     | attendence   | 2018-02-15T11:00:00 | event_id:12345,subscriber_id:1,token:a2s3x2fer,status:attended | xyz hospital | 1      |
+
+
+@unit @Negativeregression  
+Scenario Outline: Create a new Log of Scheduler API Unit and Regression Negative Testing
+
+Given the invalid inputs for the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a log for role "<logger_role>" with its Id "<logger_id>" "<entity_id>" for category "<log_category>" from time period of "<datetime>" with data as "<log_data>"
+When a POST request for an endpoint /log/new/ is triggered to create new log for scheduler block
+Then response code of negative testing POST request for invalid data is "<status_code>"
+
+
+
+Examples:
+  | requestor_id | requestor_role | logger_role | logger_id | entity_id | log_category | datetime            | log_data                                                       | status_code |
+  | healthngo1   | healthworker   | resource    | 1         | 67890     | attendence   | 2018-02-15T11:00:00 | event_id:12345,subscriber_id:1,token:a2s3x2fer,status:attended | 400         |
+  | healthngo1   | healthworker   | entity      | 67890     | 67890     | attendence   | 2018-02-15T11:00:00 | event_id:12345,subscriber_id:1,token:a2s3x2fer,status:attended | 403         |
+  | healthngo1   | healthworker   | subscriber  |1          | 67890     | attendence   | 2018-02-15T11:00:00 | event_id:12345,subscriber_id:1,token:a2s3x2fer,status:attended | 404         |

test/features/createmessagenew.feature

@@ -0,0 +1,44 @@
+@method=POST  @endpoint=/message/new/
+Feature: Create a new message of Scheduler API
+
+Gherkin feature files for GovStack Scheduler services
+
+@smoke  
+Scenario: Create a new message of Scheduler API Smoke Test   
+
+Given the requestor Id is "healthngo1" with role as "healthworker" to create a new message
+When a POST request for an endpoint /message/new/ is triggered to create new message for scheduler block      
+Then the result should return message Id as "1" for smoke testing
+And response code of POST request is "200" for smoke testing 
+
+
+
+@unit @happyregression  
+Scenario Outline: Create a new message of Scheduler API Unit and Regression Happy Testing
+
+Given the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a message with details like "<entity_id>" "<category>" with message body as "<message_body>" 
+When a POST request for an endpoint /message/new/ is triggered to create new message for scheduler block
+Then the result should return message details like "<message_name>" and "<message_id>" for requested message
+And response code of POST request is "200"
+
+Examples: 
+  | requestor_id | requestor_role | entity_id | category | message_body                        | message_name | message_id |
+  | healthngo1   | healthworker   | 67890     | reminder | you have a doctor consultatio today | xyz hospital | 1          |
+
+
+@unit @Negativeregression  
+Scenario Outline: Create a new message of Scheduler API Unit and Regression Negative Testing
+
+Given the invalid inputs for the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a message with details like "<entity_id>" "<category>" with message body as "<message_body>"
+When a POST request for an endpoint /message/new/ is triggered to create new message for scheduler block
+Then response code of negative testing POST request for invalid data is "<status_code>"
+
+
+
+Examples:
+  | requestor_id | requestor_role | entity_id | category    | message_body                        |  status_code |
+  | healthngo1   | healthworker   | 67890     | reminder    | you have a doctor consultatio today |  400         |
+  | healthngo1   | healthworker   | 67890     | appointment | you have a doctor consultatio today |  403         |
+  | healthngo1   | healthworker   | 67890     | invite      | you have a doctor consultatio today |  404         |
+
+

test/features/createnewentity.feature

@@ -0,0 +1,44 @@
+
+@method=POST  @endpoint=/entity/new/
+Feature: Create a new entity of Scheduler API
+
+Gherkin feature files for GovStack Scheduler services
+
+@smoke  
+Scenario: Create a new entity for Scheduler API Smoke Test   
+
+Given the requestor Id is "healthngo1" with role as "healthworker" to create a new entity
+When a POST request for an endpoint /entity/new/ is triggered to create new entity for scheduler block      
+Then the result should return entity Id as "67890" for smoke testing
+And response code of POST request is "200" for smoke testing 
+
+
+
+@unit @happyregression  
+Scenario Outline: Create a new entity for Scheduler API Unit and Regression Happy Testing
+
+Given the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a entity with name "<name>" for "<category>" with following details like "<phone>" "<email>" with "<website>"
+When a POST request for an endpoint /entity/new/ is triggered to create new entity for scheduler block
+Then the result should return entity details like "<entity_id>" and "<entity_name>" for requested entity
+And response code of POST request is "200"
+
+Examples: 
+  | requestor_id     | requestor_role | name       | category |phone           | email         | website     | entity_name    | entity_id | 
+  | healthngo1       | healthworker   | practo     | hospital | 9980555504     | abc@gmail.com | www.abc.com | hospital       | 67890     | 
+
+
+@unit @Negativeregression  
+Scenario Outline: Create a new entity for Scheduler API Unit and Regression Negative Testing
+
+Given the invalid inputs for the requestor id is "<requestor_id>" with role as "<requestor_role>" to create a entity with name "<name>" for "<category>" with following details like "<phone>" "<email>" with "<website>"
+When a POST request for an endpoint /entity/new/ is triggered to create new entity for scheduler block
+Then response code of negative testing POST request for invalid data is "<status_code>"
+
+
+
+Examples:
+  | requestor_id | requestor_role | name   | category    | phone      | email          | website          |  status_code |
+  | healthngo1   | healthworker   | practo | hospital    | 9980555504 | sree@gmail.com | http://alert.com |  400         |
+  | healthngo1   | healthworker   | practo | education   | 9980555504 | sree@gmail.com | http://alert.com |  403         |
+  | healthngo1   | healthworker   | practo | agriculture | 9980555504 | sree@gmail.com | http://alert.com |  404         |
+