Add a new "Did you know" section, or maybe call it Test Design Best Practices

[MohabMohie]

this section should show some hints
or tips and tricks

• like using fluent design to chain actions and validations
• using By objects / dynamic element identification / not @findby / handling android and ios with different locators in the same project
• when to have android and ios in the same project and when to separate them
• using Allure annotations to export BDD-like business-readable reports (instead of using cucumber itself)
• not using priority to order tests, with guidance on test cases (isolated) and test scenarios (depends on methods)
• running tests from a ci/cd pipeline -> reference to properties
• paths to the artifacts that should be attached (allure, extent, summary)
• testing pyramid / automation strategy and the importance of each level of testing
• test automation tool selection criteria
• test automation architecture (where shaft fits)
• test automation solution design (pom, fluent, anonymous, inheritance, base classes)