Test account standardization - NextensArelB/SwaggerGenerationTool GitHub Wiki
[[TOC]]
As part of our efforts to improve the security and oversight of our test accounts we need to make sure all test accounts are equivalent in terms of password security, naming stucture etc. This will help make it clear to anyone at Nextens, what each test account is used for and maintain the same security for each account. This standardization helps to enhance security and make testing more organized and structured.
Each asset will have it's own test account that is maintained by it's respective team. There will also be a clear distinction between which accounts are used for Test Automation or Manual testing. As well as which environment the testing is for in regards to test data. With+ these structures it is clear, which asset, which environment and it's use.
The new naming convention for test accounts was defined in order to make sure it is clear and easy to follow and replicate. The goal of which is mentioned in the paragraph above. The naming convention is as follows:
type [email protected]
If sub (Subscription) and env (Environment) is not relevant they can be left out.
For example, if we want to create a Naslag account that does test automation for the Financial subscription with test data for dev05:
If we want to create a manual test account for Naslag that does not have a subscription or environment as test data is not relevant:
As shown above, the only required aspects of the naming convention is the asset name and if the testing is done manually or automated.
Why is it important to clarify which accounts are used for automation and which are used for manual testing?
This clarification can prevent test failures. An all too common occurrence is that test data that is required for specific tests to work. Someone might use an account that is meant for TA for some manual testing and as a result of their use the test data will change. Then that would lead to the pipelines karate tests failing, as their required data is no longer present. With the new naming convention if an account is called TA then that account should not be used for any other purposes. And any account that has Man in it is used purely for manual testing and no other reason. This makes sure that all test accounts are used correctly and can not cause problems for any other tests.