{"id":18771782,"url":"https://github.com/zahid-automate/case-studies","last_synced_at":"2026-01-26T01:32:15.615Z","repository":{"id":170862255,"uuid":"591401916","full_name":"Zahid-Automate/Case-Studies","owner":"Zahid-Automate","description":"Case Study on Test Automation","archived":false,"fork":false,"pushed_at":"2023-01-20T17:26:56.000Z","size":2,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-05-21T01:13:58.438Z","etag":null,"topics":["test-automation","testing"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Zahid-Automate.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-01-20T17:07:35.000Z","updated_at":"2024-04-06T22:03:28.000Z","dependencies_parsed_at":null,"dependency_job_id":"2fbd029f-f93a-40d6-901e-7f4d09c3331a","html_url":"https://github.com/Zahid-Automate/Case-Studies","commit_stats":null,"previous_names":["zahid-automate/case-studies"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Zahid-Automate/Case-Studies","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Zahid-Automate%2FCase-Studies","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Zahid-Automate%2FCase-Studies/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Zahid-Automate%2FCase-Studies/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Zahid-Automate%2FCase-Studies/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Zahid-Automate","download_url":"https://codeload.github.com/Zahid-Automate/Case-Studies/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Zahid-Automate%2FCase-Studies/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28763934,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-26T00:37:26.264Z","status":"ssl_error","status_checked_at":"2026-01-26T00:37:25.959Z","response_time":113,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["test-automation","testing"],"created_at":"2024-11-07T19:26:37.786Z","updated_at":"2026-01-26T01:32:15.608Z","avatar_url":"https://github.com/Zahid-Automate.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Case-Study on Test Automation \n\nAs applications and systems grow larger and more complex, test automation is moving beyond a luxury and becoming a necessity for them. As technology changes, testing must also change and adapt. So start small, by using different approaches on a small scale to see what works best before attempting to spread further.\n\nSuccessful test automation needs both ingenuity and perseverance.\n\nWhat are the main factors that contribute to success in test automation? What common factors most often lead to the failure of an automation effort?\n\nThere are no simple universal answers to these questions, but some common elements exist. Two of them are management issues and the testware architecture:\n\n- \u003cb\u003eManagement support for automation,\u003c/b\u003e such as setting realistic objectives and providing sufficient and appropriate resources to achieve a planned return on investment (ROI).\n\n- \u003cb\u003eA good technical architecture for automated testware,\u003c/b\u003e having the right levels of abstraction to give flexibility and adaptability while minimizing costs, not just of testware maintenance, but of all aspects of automation.\nOverview\n\n\nAdded value / benefits\n- \u003cb\u003ePerforming a daily check of the test environments\u003c/b\u003e (9 environments, in place for 1 year)\n\n       - manually \\~30 minutes/environment\n\n       - automated \\~15 minutes/environment\n        \n- With automated tests, we are \u003cb\u003eable to identify, within minutes, major configuration issues \u003c/b\u003e(e.g. deployment problems, services not started).\n\n- We sometimes \u003cb\u003efind bugs that are not found by manual test execution.\u003c/b\u003e\n\n- Manual testers have \u003cb\u003emore time for exploratory testing \u003c/b\u003e since they don`t have to perform the tests that are already automated.\n\n- \u003cb\u003eFunctional\u003c/b\u003e (test cases) coverage.\n\n- \u003cb\u003eNumber of releases/ year.\u003c/b\u003e\n\n- 2013(regression testing done manually) - 4 releases/year\n\n- 2015(regression testing done automatically + manually) - 8 releases/year\n\n\u003cb\u003e=\u003e GAIN:\u003c/b\u003e doubled the number of releases in a 2-year time span\n\n## HOW - case ## \n### Introduction ###\n- Automation testing is part of the development life cycle (with continuous delivery)\n\n- Independent team, working with Scrum (testers \u0026 developers)\n\n- Defined and documented way of working\n\n- Support from Architect for the testing approach \u0026 senior developers for technical reviews\n\n### Phases ###\n\n- Pilot - goal: Define Strategy and Approach by trying to automate various parts of the systems\n\n- Phase 1 - goal: Automate first subset of tests, which forms environment morning check [\\~30 tests]\n\n- Phase 2 - Goal: Extension of morning check [400+ tests]\n\n- Phase 3 - Goal: Regression test suite\n\n### CI runs ###\n- All development environment + Integration + Acceptance\n\n- Team City\n\n- Schedule\n\n### Frontend tests ###\n- Are done by clicking links and comparing elements\n\n- All tests are independent\n\n- Can be executed for each browser\n\n- Tests are written based on A-A-A (arrange-act-assert) pattern\n\n- Usually, it's a check if an element exists or if an element contains a certain value.\n\n- Screenshots are made if tests fail\n\n### Backend tests ###\n- Tests are written based on A-A-A (arrange-act-assert) pattern\n\n- All tests are independent\n\n- Ping tests check if a call can be made\n\n- Quick scan tests simulate a user using application by calling all calls without frontend\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fzahid-automate%2Fcase-studies","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fzahid-automate%2Fcase-studies","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fzahid-automate%2Fcase-studies/lists"}