In the software development lifecycle, testing plays a vital role with respect to quality assurance and quality control of any project.
Automated testing saves a lot of time when building and releasing different versions of a project.

It becomes a tedious task for a QA team to do manual testing after each iteration for same functionality repeatedly.
In this post, I will share a few tips and tricks to writing test cases for different testing scenarios.

Specifically, let’s look at writing automated test cases for an AEM-based project.
There are different modules in AEM: the core bundle, which includes OSGI services, sling servlets, ad sling models; and ui.apps, which includes AEM components, AEM pages, templates, and HTML markups.

As a project and code base grows, it is really important to make sure that test coverage for the code is there to maintain consistency and sanity.
Writing test cases for AEM is different from writing conventional Java test cases, and this can make it difficult for a beginner to write test cases for AEM application

Next, these dependencies need to be added in parent pom.xml:

<dependencies>

    ...

    <!-- Testing -->

     <dependency>

         <groupId>org.junit</groupId>

         <artifactId>junit-bom</artifactId>

         <version>5.5.2</version>

         <type>pom</type>

         <scope>import</scope>

     </dependency>

     <dependency>

         <groupId>org.slf4j</groupId>

         <artifactId>slf4j-simple</artifactId>

         <version>1.7.25</version>

         <scope>test</scope>

     </dependency>

     <dependency>

         <groupId>org.mockito</groupId>

         <artifactId>mockito-core</artifactId>

         <version>2.25.1</version>

         <scope>test</scope>

     </dependency>

     <dependency>

         <groupId>org.mockito</groupId>

         <artifactId>mockito-junit-jupiter</artifactId>

         <version>2.25.1</version>

         <scope>test</scope>

     </dependency>

     <dependency>

         <groupId>junit-addons</groupId>

         <artifactId>junit-addons</artifactId>

         <version>1.4</version>

         <scope>test</scope>

     </dependency>

     <dependency>

         <groupId>io.wcm</groupId>

         <artifactId>io.wcm.testing.aem-mock.junit5</artifactId>

         <!-- Prefer the latest version of AEM Mock Junit5 dependency -->

         <version>2.5.2</version>

         <scope>test</scope>

     </dependency>

    ...

</dependencies>