Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Scope of improvement: Action Items In progress: Sprint-4 and Sprint-5

Internal Review and Tarun findings (Common points):

  1. Identify common Constant params across automation file system and mark to call data calls dynamic. Ex : https://github.com/egovernments/test-automation/pull/6/files#diff-ea737e3a692338e13d7664c7215c1b9e65232aa7d339d4a0e419856aa76cb018

  2. Automation code Readability practice with proper documentation for re-usages, fixes understanding.

Tarun’s Review findings:

  1. Focus required to transit automation code into platform independent (QA, UAT, Dev).

  2. Avoid hard coding of data population and implement automation flow to clear data post automation runs

  3. End to End work flows implication by extending action flow beyond end point request and responses. This requires efforts to make sure services and functionality work flows at API levels are tested.

  4. Find and implement logic to auto populate test-data before we start test runs instead having it set of pre-filled data

Automation team Internal Reviews:

  1. Rename with relevant naming for websCommonHeaders, oauthTokenHeader, karate-config, jsUtils

  2. CONSTANTS, tags (@success_workflow) etc should we use camel case etc

Use Camel case for all tag names, service naming Uniformly across automation suite

4. Work flow Calls optimisation:

https://github.com/egovernments/test-automation/pull/6/files#diff-5f5bba3780c6d1163855065fa11b9fb9a82e17ef6958f8a82cfd7f1a422becfd

  • No labels