Merge branch 'develop' into 'main'

Develop

See merge request !4

.gitlab-ci.yml

+# This file is a template, and might need editing before it works on your project.
+# To contribute improvements to CI/CD templates, please follow the Development guide at:
+# https://docs.gitlab.com/ee/development/cicd/templates.html
+# This specific template is located at:
+# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml
+
+# This is a sample GitLab CI/CD configuration file that should run without any modifications.
+# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
+# it uses echo commands to simulate the pipeline execution.
+#
+# A pipeline is composed of independent jobs that run scripts, grouped into stages.
+# Stages run in sequential order, but jobs within stages run in parallel.
+#
+# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
+
+stages:          # List of stages for jobs, and their order of execution
+  - test
+
+unit-test-job:   # This job runs in the test stage.
+  stage: test    # It only starts when the job in the build stage completes successfully.
+  script:
+    - echo "Running unit tests..."
+    - ./hac_test.sh
\ No newline at end of file

README.md

@@ -33,13 +33,16 @@ In 'hac', 'has', and 'hac.dict' code, look for '# ATTENTION:'. Check and change
 - hpssadm
 
 ## Implementing new hac commands ##
-Add new commands to hac.dict.
+Add new commands to hac.dict and add unit tests for each new 'hac' command you implemented to 'hac_test.sh'.
 
 ## License ## 
 'hac and has' is published under GNU GENERAL PUBLIC LICENSE Version 3.
 
 ## Contributing ##
-If you wish to contribute to this project, please, first, crete your own branch and do your changes there. After you are ready create a merge request in Gitlab with 'develop' as a target branch - here are instructions: https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html .
+If you wish to contribute to this project, please:
+- crete your own branch and perform your changes there;
+- add unit tests for each new 'hac' command you implemented to 'hac_test.sh'.
+- when you are ready create a merge request in Gitlab with 'develop' as a target branch - here are instructions: https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html .
 
 Please be aware that your changes will be published under GNU GENERAL PUBLIC LICENSE Version 3.