Skip to content

Conversation

@Farcasut
Copy link
Contributor

No description provided.

Farcasut added 30 commits August 2, 2023 22:44
*I added the classes need to interact with the configs from Analytics.Code.COnfiguration and I also added a class that will normalise the jsons from matomo
* I added the scripting service and the MatomoAnalyticsManager
*I added the livetable and everything seems to work okay for the time being.
* I modified the implementations of the JsonNormaliser to be a component and I also added the url + the document reference to the returned json.
* I restructured the packages and replaced the URLBuilder with a proper one.
* I added some comments. The final version of the pr.
* I added an if in the case that I switch back to the getPageTitles API
* I modified the dependencies and removed some parameters.
* I modified how I get the normaliser
* I added 2 tests and modified a few typos.
* Renamed the MostViewed hint to MostViewedPages and modified the comments
* Renamed 2 pages and added a test class for MatomoAnalyticsManager
*Changed the name of a file
* I added a test for the MatomoANalyticsManager
* I added new error messages and I updated the comments ona few functions.
* I added the JSON normalizer to transform the Matomo result into a format that can be easily processed in JavaScript for the Chart.js library. I also added two new Velocity macros and the JS code for displaying the evolution.
* I added a test for the RowEvolutionJsonNormaliser and added comments to the javascript code.
* Removed unused livetable fields
* Dosen't work for the time being I can't connect to the matomo application from the testing container.
* Test for the description button
* Added a few functional tests for the basic operations of the extension.
@Farcasut Farcasut linked an issue Nov 24, 2023 that may be closed by this pull request
@Farcasut Farcasut self-assigned this Nov 24, 2023
@Farcasut Farcasut added this to the 1.0 milestone Nov 24, 2023
@Farcasut Farcasut marked this pull request as ready for review November 24, 2023 10:06
Copy link
Contributor

@mflorea mflorea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your code needs significant refactoring. I recommend checking the page objects and tests from XWiki platform to take inspiration from.


public class Config
{
public static final String DB_CONTAINER_NAME = "farcasut/custom-mysql:latest";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test needs to run on CI. I doubt this custom Docker container is published somewhere, but even if it is, we should use an official container.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The container is currently publicly hosted on Docker Hub, but do you think it would be a better choice to create the container from scratch? Like using the default container and populating the database using the API provided by TestContainers

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Long term we should move the container to an xwikisas account on Docker Hub.

*
-Update the poms.xml
-Moved from a class with static methods to a normal one

public class Config
{
public static final String DB_CONTAINER_NAME = "farcasut/custom-mysql:latest";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Long term we should move the container to an xwikisas account on Docker Hub.

@snazare snazare removed this from the 1.0 milestone Jan 16, 2024
Added a FindBy to select the elements in the config tab
Removed unnecessary imports
Renamed classes
Modified the URL of the rowevolution request to have the get action insted of the view
Added a wait to avoid flickering
@Farcasut Farcasut force-pushed the functionalTests branch 2 times, most recently from 7f090f7 to 05114fe Compare February 15, 2024 14:11
Refactored code, added a new test and improved formatted the code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create functional tests

4 participants