search

wttech / bobcat

Bobcat is an automated testing framework for functional testing of web applications.
https://cognifide.github.io/bobcat/
Apache License 2.0
90 stars 40 forks source link

Handling AEM Core components #373

Open mkrzyzanowski opened 5 years ago

mkrzyzanowski commented 5 years ago

Adobe maintains a set of core components: https://github.com/adobe/aem-core-wcm-components.

The scope of this task is to investigate if Bobcat can handle authoring using these components and add such capability wherever it is not possible.

Note: we're assuming the latest version of Core components

Environment:

Components:

Template components

Page authoring components

Container components

Form components

kaczymuczy commented 5 years ago

I'll join, will take care of Title first

kaczymuczy commented 5 years ago

Next on my list is List

kaczymuczy commented 5 years ago

Text is already covered by ConfigureComponentTest - checking it on the list as "done"

kaczymuczy commented 5 years ago

Next - Image

jaskowskak commented 5 years ago

Hi, I take care of Teaser component

DeChrish commented 5 years ago

@kaczymuczy @jaskowskak @mkrzyzanowski Good Job!!

Danon9111 commented 5 years ago

I will take a look on Download component

EDIT: Regarding AEM properties Download component is deprecated since 6.5 version image

barbasial commented 5 years ago

I'm joining too. I will take care of Button component.

kaczymuczy commented 5 years ago

I'll put the Content Fragment now under my looking glass

Danon9111 commented 5 years ago

I will take a look on the Separator component

jaskowskak commented 5 years ago

I'll take care of Carousel

Danon9111 commented 5 years ago

Separator is a core component and available in AEM 6.5. Unfortunately it is not available (by default) under We Retail content. It is available only under component demo pages (../content/core-components-examples/library).

We can make it available by modifying default configuration of 'content-page' template under We Retail branch. (This need to be confirmed, if is it possible to automate this action)

We can also prepare tests for Separator component, which will work under path

/content/core-components-examples/library

Or we can drop this component.

@mkrzyzanowski @Shaihuludus what do you think?

P.S. As I heard there is bigger number of components whit similar situation. Maybe it would be valuable to verify which components?

jaskowskak commented 5 years ago

Tests for Teaser component: https://github.com/Cognifide/bobcat-aem-tests/pull/12

Danon9111 commented 5 years ago

Creating tests for Separator component will be dropped. Reasons behind it are:

I have also noticed that in Core Components 2.6.0 is added new component - Experience Fragment and in Core Components 2.7.0 Embed . Do we want add them to the list and create tests for them?

Danon9111 commented 5 years ago

I will try Sharing component this time ;)

Danon9111 commented 5 years ago

Sharing component need some special configuration of page properties. We can achieve this by "hard coding" this properties, but after that we don't have anything to automate. Other way is to create mechanism in Bobcat to set proper page properties. For this purpose I have create issue in main Bobcat repo - https://github.com/Cognifide/bobcat/issues/393

For now, there is no sense to create any tests for Sharing component.

Danon9111 commented 5 years ago

I will work on breadcrumb right now

barbasial commented 5 years ago

I will try Accordion

kaczymuczy commented 5 years ago

I'm going for the Content Fragment List

kaczymuczy commented 5 years ago

Working on Tabs now

kaczymuczy commented 5 years ago

Going for Form Container

kaczymuczy commented 5 years ago

Actually I'll take all Form Components should no one protest :)