DanielaSogei
commented
2 months ago Diffusione Limitata
Hi, I’m not able to assign task to other Sogei’s colleagues, except Paolo Tartara. Why I’m not able to assign to other colleagues as Enrico Chiacchiari and Alessandro Innocenti? They are not listed in the the Assignees. Thanks Daniela
Da: RafyMehany @.> Inviato: martedì 16 aprile 2024 14:38 A: glaciation-heu/IceStream @.> Cc: PIERNERA PALMIERI DANIELA @.>; Assign @.> Oggetto: [glaciation-heu/IceStream] [Live analytics, edge computation] Component smoke tests for MEF/SOGEI (Issue #144)
Non si ricevono spesso messaggi di posta elettronica da @.**@.>. Informazioni sul perché è importantehttps://aka.ms/LearnAboutSenderIdentification Task
Specify and run smoke tests for the Deployed service/component, the Goal is to run some tests against your service after its deployment on the Kubernetes cluster to make sure that it is working as expected, you can achieve this task manually for now but later on, you will automate this. This task involves setting up smoke tests for the service/component deployment, ensuring the reliability and stability of the deployed application.
1- Design Smoke Tests
Smoke Test Specification: Specify smoke tests to verify critical functionalities and basic usability of the deployed service/component. To accomplish this task effectively, it's essential to have access to the deployed service/component and sufficient knowledge of its functionalities and dependencies.
2- Document this smoke tests
Update Documents: Update your documents to include your smoke tests so anybody can refer to them, and later on when you automate it, it will be documented so it will save time.
3- Run Smoke Tests
Run your tests after every deployment on the integration cluster to make sure that the service is working as expected.
Example:
- Specify the critical and basic functionalities that the smoke tests will cover.
- Provide these smoke tests, like curl or API requests that you will fire to make sure that the service is working as expected after deployment
- Provide the expected results for each test.
- Provide the steps to run the smoke tests.
- Provide the steps to interpret the results.
- Update the documentation to include the smoke tests with the results.
4- Integration with Deployment Workflow (This step is optional for now)
Integration with Deployment Workflow: Integrate smoke testing into the deployment workflow to automate the process and ensure it runs seamlessly alongside other deployment steps. you can achieve this using argoCD rollouts for more information check this docshttps://argo-rollouts.readthedocs.io/en/stable/
Acceptance Criteria
- [ ] Proper access to the environment.
- [ ] Smoke tests are documented and cover critical functionalities.
- [ ] Smoke tests are run after every deployment on the integration cluster.
- [ ] Smoke testing is integrated into the deployment workflow (This is an option step for now)
Note
- Ensure that smoke tests provide quick feedback on the health of the deployed service/component.
- Smoke tests should be designed to run efficiently without significantly impacting the deployment process.
- You will have to do the smoke testing every time after a new deployment on the integration cluster.
Additional Information
— Reply to this email directly, view it on GitHubhttps://github.com/glaciation-heu/IceStream/issues/144, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6PPCZQQH722FYAV4OYEFGDY5ULRBAVCNFSM6AAAAABGJIMZYGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2DKOJTHAZTKOI. You are receiving this because you were assigned.Message ID: @.**@.>>
Le informazioni contenute in questo messaggio di posta elettronica sono da considerarsi riservate e confidenziali. Il loro utilizzo è consentito esclusivamente al destinatario in indirizzo e ne è vietata la diffusione in qualunque modo eseguita, salvo che ne sia data espressa autorizzazione dal mittente. Nel caso in cui il messaggio Le fosse pervenuto per errore, La invitiamo gentilmente ad eliminarlo in modo permanente dopo averne dato tempestiva comunicazione al mittente e a non utilizzare in alcun caso il suo contenuto. Qualsivoglia utilizzo non autorizzato di questo messaggio e dei suoi eventuali allegati espone il responsabile alle relative conseguenze civili e penali.
This communication is confidential and the use of the contained information is allowed solely for the intended recipient. Its disclosure, distribution or copying is prohibited, unless expressly authorized by the sender. If you receive this communication by mistake please notify us and delete the message and its attachments. Anyone responsible for the unauthorized use of this message and its attachments is liable to face legal consequences.
RafyMehany
Task
Specify and run smoke tests for the Deployed service/component, the Goal is to run some tests against your service after its deployment on the Kubernetes cluster to make sure that it is working as expected, you can achieve this task manually for now but later on, you will automate this. This task involves setting up smoke tests for the service/component deployment, ensuring the reliability and stability of the deployed application.
1- Design Smoke Tests
Smoke Test Specification: Specify smoke tests to verify critical functionalities and basic usability of the deployed service/component. To accomplish this task effectively, it's essential to have access to the deployed service/component and sufficient knowledge of its functionalities and dependencies.
2- Document this smoke tests
Update Documents: Update your documents to include your smoke tests so anybody can refer to them, and later on when you automate it, it will be documented so it will save time.
3- Run Smoke Tests
Run your tests after every deployment on the integration cluster to make sure that the service is working as expected.
Example:
4- Integration with Deployment Workflow (This step is optional for now)
Integration with Deployment Workflow: Integrate smoke testing into the deployment workflow to automate the process and ensure it runs seamlessly alongside other deployment steps. you can achieve this using argoCD rollouts for more information check this docs
Acceptance Criteria
Note
Additional Information