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

Create tests for vessel-charging/messages/ProviderStatusMessageParams using jest. #27

Open
9 tasks
haialaluf opened this issue Sep 5, 2018 · 6 comments
Open
9 tasks

Comments

@haialaluf
Copy link
Contributor

first-timers-only

This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

Find more first-timers-only issues from DAV Foundation here.

Thank you for your help ❤️

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

dav-js

This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.

How you can help

The Issue

Create tests for vessel-charging/messages/ProviderStatusMessageParams using jest.

You need to create tests to check that the serialize and deserialize methods work as expected.

Please use the test file for class NeedParams as a basis for your new code.

  • Function serialize in class MessageParams must return a JSON object that contains all properties defined in the MessageParams instance.

  • Function deserialize in class MessageParams receives a JSON string and must initialize all the properties of the MessageParams instance with the values in the JSON string.

messageParams1.desrialize(messageParams2.serialize()) == messageParams2 must therefore always be true.

NOTE: Some names are changed between protocol string representation of instance properties:

  • location is internally represented as { lat , lon } but serialized as { latitude , longitude }
  • Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

Contributing to dav-js

  • Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
  • Comment in this issue that you would like to do it.
  • Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
  • Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
  • Code Code Code
  • Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
  • Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
  • Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
  • Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

@rashmithajunoothula
Copy link

Hi, I am a newbie to open source and would like to handle this issue

@TalAter
Copy link
Member

TalAter commented Sep 17, 2018

Please go ahead @rashmithajunoothula 👍

@TalAter
Copy link
Member

TalAter commented Sep 18, 2018

@rashmithajunoothula I believe there is a bug in all the message files for vessel-charging which will cause you to not be able to complete this issue.

I'll update here once we fix this.

@TalAter
Copy link
Member

TalAter commented Oct 2, 2018

@rashmithajunoothula The bug has been resolved. Are you still interested in doing this issue?

@bicep
Copy link

bicep commented Dec 18, 2018

HI @rashmithajunoothula are you still interested in this? I'd love to work on some tests in the meanwhile. Perhaps I should take this @TalAter

@mariolo1985
Copy link
Contributor

Hi @rashmithajunoothula would you still like to resolve this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants