Docker Artefacts Testing
What if the testing scope changed from usual UI or API testing? Instead, the testing scope gets diverted to the testing of base images (let's say python, node) based on Docker used in the Dev or QA community. While tackling this problem statement, finding answers to the next set of questions are very important -
1. How to test this ecosystem?
2. What will be the goals of testing?
3. What the test pyramid will look like? Key Takeaways:
1. What is a Docker heavy application? What does it look like?
2. Different testing perspectives? ? adding unit tests, evaluating security and performance?
3. Test Automation
4. Pipeline designing
5. Answer to 'Will the strategy remains the same for Daemonless?'
Monika Sharma, Senior Consultant, ThoughtWorks
Monika is a QA enthusiast with experience in both functional and non-functional testing. She has expertise in creating testing strategies for projects. She has gained extensive experience in micro-services testing using rest-assured and JS-based libraries, and web-app testing with cypress and taiko. She also has proficient experience in performance testing using Gatling and K6, infrastructure testing for Dockers.