Create tests for `src/drone-charging/MessageParams.ts` using jest.

[mariolo1985]

first-timers-only

This issue is tagged 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 repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.

How you can help

In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.

Here is a good opportunity to simplify one of our tests.

The Issue

We currently do not have unit testing set up for src/drone-charging/MessageParams.ts. Please create Jest tests for the serialize() and deserialize() methods.

A good reference point would be src/ride-hailing/MissionParams.test.ts and customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint. Also, you can reach out to our gitter channel with any questions 😄

The test you write will be similar to this:

import MessageParams from './MessageParams';

describe('MessageParams class', () => {
  let messageParams: MessageParams;
  let serializedMessageParams: any;

  beforeEach(() => {
    messageParams = new MessageParams({
      senderId: undefined
    });

    serializedMessageParams = {
      protocol: 'drone_charging',
      type: 'message',
      senderId: undefined,
      ttl: undefined
    };
  });

  describe('serialize method', () => {
    it('should return serialized MessageParams object with the current values', () => {
      expect(messageParams.serialize()).toEqual(serializedMessageParams);
    });
  });

  describe('deserialize method', () => {
    it('should return a MessageParms instance', () => {
      const messageParamsObject = new MessageParams();
      messageParamsObject.deserialize(serializedMessageParams);
      expect(messageParamsObject).toBeInstanceOf(MessageParams);
    });

    it('should return deserialize MessageParams instance with the current parameters', () => {
      const messageParamsObject = new MessageParams();
      messageParamsObject.deserialize(serializedMessageParams);
      expect(messageParamsObject).toEqual(messageParams);
    });
  });
});

After making your changes, run npm run tslint and npm run jest to make sure our tests are passing.

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
• Install dependencies by running npm install
• 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 😄

[lucasheim]

I can do this one too.

[mariolo1985]

Hi @lucasheim that's great 😄 we love the enthusiasm! If you could work on one issue and one PR at a time, that will help us review PRs better. This also allows more contributors to work on more issues. Could you let us know which issue you would like to claim?

[lucasheim]

Sure, this one.

[mariolo1985]

Excellent! This one is yours 👍