Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests and continuous integration for this repo #34

Open
Frijol opened this issue Jul 11, 2017 · 5 comments

Comments

@Frijol
Copy link
Member

commented Jul 11, 2017

No description provided.

@rwaldron

This comment has been minimized.

Copy link

commented Jul 17, 2017

Will this be a rgsoc task? I think that's a great assignment :)

@brihijoshi

This comment has been minimized.

Copy link

commented Jul 27, 2017

Hi, we are excited to start working with this. Could you help us know how to start? It's a bit confusing 😅

@rwaldron

This comment has been minimized.

Copy link

commented Jul 27, 2017

@tikurahul can you offer some guidance? Thanks!!

@tikurahul

This comment has been minimized.

Copy link
Contributor

commented Jul 27, 2017

Sorry, the README is a bit lacking on how to get started with this codebase.

This project uses Google App Engine's Python runtime. So you will need to install the Google Cloud SDK and setup the App Engine python runtime.

Once you do that, you will have dev_appserver.py on your PATH to run this application locally.

You will also need to tweak a few more things.

You will need to create a test GitHub repo which will be used to create issues and comments when crash reports are submitted. For that you will need to make changes to github_utils.py to pick up the organization and the repo_name from an environment variable.

You will also need a GItHub personal access token to make authenticated requests to this repo. This will be stored in a file called debug_client_secrets.json.

--

Once you make these small changes, you will be able to run the entire application locally. This you can do using dev_appserver.py . from the root folder for the project (which contains app.yaml).

I think for tests, you can look at using headless chrome to drive crash report submissions to make sure:

  • A crash report shows up correctly with the appropriate metadata
  • It gets correctly de-duped
  • An issue is created in GitHub if one does not exist already.

I am going to add some more information to the README.md which will help you, but this should unblock you for now.

@brihijoshi

This comment has been minimized.

Copy link

commented Jul 28, 2017

@tikurahul Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.