🚩 NEW Ticket - DEBUG End-to-End Testing

✅ Drafted ticket
✅ Added Prashant to github project as a member
✅ Pinged Prashant for stepping into new ticket

DRAFT Checklist

• [Mervin] INSTALLED Latest plugin on develop.gatherpress.org
• [Mervin] ?? UPDATE develop.gatherpress.org with fresh clone of PROD
• WRITE Fresh end-end tests (?Playwright)
• DOCUMENT how to execute tests (?commit message / else?)

RE Scenarios

1. Plugin Installation + Activation
2. Publish an Event
3. Respond to RSVP "Attending"

Hi @mauteri
we would like to know the user scenarios/test cases for test automation.

@MervinHernandez mind working with them on this? Thanks.

@prashantabellad leta begin with the checklist I outlined here, and expand these tests later.

Hi, @MervinHernandez @mauteri,
I analyzed the scenarios and noted down the steps to perform action and validate scenarios. Please let me know if it is good to start writing the automation tests.

Test Scenario Steps:

Plugin installation + activation.

• Log in to [dev.gatherpress.org/wp-admin] (http://dev.gatherpress.org/wp-admin).

• Click on Plugins, from the left side menu.

• Click on Activate text below the plugin name, to activate the plugin.

  Validate:

• Verify that the user is on plugin page. (verify the page url.)
• Verify the Add New Plugin button.
• Verify that the list of plugins is visible on the plugin menu page.

Publish an Event.

• Log in to dev.gatherpress.org/wp-admin.

• Click on Event, from the left side menu.

• Click on the Add New Event button.

• Add title to the event, select date and time, and select venue of event.

• Click on publish button.

  Validate:

• Verify that the user is on the event page.
• Verify that the user can add new event to the application.
• Verify that the added event is visible on the event page.

Respond to RSVP “Attending”.

• Log in to dev.gatherpress.org
• View the latest event.
• Click on RSVP button.
• Log in to the application.
• View the attendance list.

Validate:

• Verify that the user can view upcoming events on home page of gatherpress.org
• Verify that the RSVP button is working well. (user logins to the selected event)
• Verify that after successful login, the user should be added to the attendance list.
• Verify that the user should select the attendance status. (not attending).

✅ Reviewed game plan drafted by QA team // made a few suggestions and cleared to proceed!

@MervinHernandez @mauteri we need to decide upon the test data clean-up strategy. There are 2 ways of doing it.
cc @01Prayag

1. Delete through API before each test execution -->
   For example, here we would always create any entity of the same name across tests (say a new event by the name "GatherPress Event"). Before a test case is executing we will delete this entity created by the previous test (if present)

Issue: Here the issue is we had tried (few months back) to DELETE entities through Wordpress documented API however these transactions were not successful

2. Clean up the test generated data through a scheduled job (weekly/monthly/quarterly)
   Here we would delete the data of the test user
   Each test case would create a unique event (eg Event1, Event2 etc) for the tests to be deterministic and to be independent of each other

Other concepts for this

1. Use SpinUpWP API to execute a fresh "Clone of PROD" every week or so?
2. Manually execute "Clone of PROD" via SpinUp Dashboard every week or so?
   Would either of these be a bad idea because we need to hang on to some code in dev.gatherpress.org ?

If my idea is a bad one, then my vote is for a schedule cron job @prashantabellad

@MervinHernandez I did not understand cloning from Prod every week.

Via SpinUpWP, we can execute creating a fresh image of "develop" from Production instance.
This would replace all files and db tho.

Hi @prashantabellad when able - can you share (or confirm) what the game plan is for rolling this out fresh?
Note: Just updated gatherpress plugin in develop to latest release 0.29.2.

?? Any actions for me?

Hi @MervinHernandez, I will update you with the plan by tomorrow June 24th

Hi @MervinHernandez below is the plan:

As part of the first PR we will build below test cases:

1. The user should publish the online event.
2. The user should publish the offline event.
3. Verify that the logged- in user should view RSVP button on home page and perform RSVP action.
4. Verify that the non logged- in user should view RSVP button on home page and perform RSVP action.

The plan is to complete the above by June 26th, Wed.

For the test data clean-up strategy, on Friday @mauteri suggested that we can use a dynamic environment (temporary one) which will build the app from the main branch code and execute the tests on the same. This environment would be created fresh for each testing.
@mauteri please correct/add as deemed fit
cc @01Prayag

Hi team - considering how-if we can use Playgrounds for testing purposes.
My initial guess is no, we cannot because this is a very temporary environment that may not fit the bill for persistent tests.

I need to understand more how we can funnel a certain branch to a playground, execute tests, and then log the results.

🚩 UNABLE to Mount a Repo to Playgrounds

❌ Following testing, I was not easily able to mount a repo containing plugins and other code to a Playground.

Recommending we Stick with Known Git Workflows

Suggesting we discuss staying with known development site + github repo workflows, for testing and managing a develop instance.
See June 22 recommended approach.

graph TD
    A[GP Repo Feature Branch X] --> B[Merge Operation]
    B --> C[Deploy Bot]
    C -->|Automatic| D[⭐ PUSH Update to develop.gatherpress.org]
    D --> E[Automated tests executed]

🔔 NEXT Actions

1. Mervin-Carsten meet to discuss how playground may be leveraged successfully for end-to-end testing
   • Scheduling for this call is in the works as of this writing.
2. [if needed] Mervin-Mike discuss sticking to more familiar methods
3. Implement the selected method + relay to QA and all team

Touched // Mervin-Carsten will try to talk now after the huddle // otherwise, we'll schedule a call.

Discussion - August 2

1 Carsten agreed = Playground would not fit the bill for end to end testing
2 Drafting new plan // mervin drew chicken scratch
3 Carsten to follow-up on the suggested approach
4 ✅ Scheduled Meeting - Aug 6 @ 4pm CT

Queued for discussion September 27

Updated the game plan - will share tomorrow during huddle.