Can i work on this issue and also please could someone provide more context?

Hi @Anujagrawal! Welcome!

You can start working on the issue, of course. It will be a pleasure to count on you and help you through the process.

But first of all I think you will need some context to pull the required repositories to get the service and the local test environment we have:

• Some context about the overall project could be useful for you to have a better understanding. In the end edit-analytics is a service that is part of a group of services that provide an Analytics API for Wikimedia projects : https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/ You will also find some sample requests to use later when you run the service locally on your laptop
  • You can even make some requests to see how edit-analytics works: https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/edits.html

About the service itself and the local testing envrionment we have to run it locally:

• edit-analytics is an API written in Go that is available at https://gerrit.wikimedia.org/g/generated-data-platform/aqs/edit-analytics
• aqs-docker-druid-test-env is a dockerized environment (you will need to install docker before) where Druid and cassandra databases are running with some sample data as a testing environment to be able to run the service locally. It's available at https://gitlab.wikimedia.org/repos/generated-data-platform/aqs/aqs-docker-druid-test-env
  • Instructions about how to run the local test environment are included in the README:
    • Just run docker build -t aqs-docker-druid-test-env . from the build folder to build the docker image
    • Run make startup from the run folder to start the local test environment
• You can also take a look at https://wikitech.wikimedia.org/wiki/Data_Platform/Systems/AQS to have an overview about all the AQS project and other services involved
  • here you will find some instructions to create and addition config-devel.yaml file to be able to run the service locally and also the way you can run the service

So, I would say that your first step here would be to be able to run the service locally and make some requests. After that, you could start working on the issue.

About the issue itself, the work here is to add an integration test cases that we missed. AQS services are serving its own API definition using a specific endpoint and we provide a test case for that endpoint. In the case of edit-analytics that case is not created yet but it's already created for the rest of the services. So, to get an idea of how to do it, you could take a look at any other service and look for that case. For example, editor-analytics is another API that uses the same test env where this integration test case is already build here

Anyway, ping us here adding a comment in the case you need additional help.
Thanks!