Category: bingo

Bingo for meetings– working at sharing meeting with others–part 4

Bingo

Bingo is a small project, written in TypeScript , and developed with Alexandru Badita in launch break (one hour - more or less). You can find sources at https://github.com/alexandru360/PresentationBingoCards/ . Those are my blog posts for Bingo : ( scroll below for the post)

Nr	Link
1	Create meeting
2	Create Tests
3	Finalize Create meeting
4	Sharing meeting
5	Keep Score
6	Add obsolete
7	Finalizing obsolete
8	End meeting
9	Dockerize tests
10	Azure CI tests
11	Yarn workspaces
12	CLI
13	Intermezzo - CLI improvements
14	typescript compile run with node
15	NestJS ,swagger and create a meeting
16	Finalizing API
17	Intermezzo - jest vs jasmine error
18	Refactor WebAPI and test service
19	Heroku Deploy NestJs
20	Angular
21	Deploy Angular to GitHub
22	WebAPI and Web
23	Documentation
24	Documentation of the code
25	Conclusions

Other use case for Bingo Meetings was Share meeting bingo(https://github.com/alexandru360/PresentationBingoCards/projects/1#card-24165765)

Share Meeting Bingo:

As a User, I can receive the meeting Id( url) . When going to this url , I can ( optionally) enter my name and check cards.

So how to implement this ? A Meeting contains an array of Cards and a array of Participants. How a Participant can check cards ?

There are several solutions for this:

The Participant can have an Id of the meeting, is going to some form of database( even in memory , like a singleton collection of Meetings), retrieve the meeting, retrieve the cards, check the card
The participant raise an event ( PleaseCheckThisCardForMe) , the meeting listens and checks the meeting
The participant have a real reference of the cards and checks the cards
The meeting has a CheckCardByParticipant that someone can call ( leaving the responsibility later – maybe on API )

We ( me and Alexandru Badita we have choosed the latest solution. So we came with the following :

public CheckCardByParticipant(c: Cards , p:Participant){
        //TODO: verify participant is added first or add
        //TODO: verify card is added first
        c.CheckMe(p);
    }

and a test

import  MeetingsFactory from '../MeetingsFactory';
import Meeting from '../meeting';
describe('Check  card basic', () => {
    it('card should be checked', () => {
        const mf=new MeetingsFactory();
        const m1=mf.CreateMeeting("andrei","first meeting");
        console.log(m1.Cards.length);
         
        expect(m1.AllUnchecked()).toBe(true);
        m1.CheckCardByParticipant(m1.Cards[0], m1.Participants[0]);    
        expect(m1.AllUnchecked()).toBe(false);
        expect(m1.IsCardCheckedByParticipant(m1.Cards[0], m1.Participants[0])).toBe(true);
         
         
   
      })
     
  })
  

Obviously, from TODO, we have to put more code and more tests – but for the moment we think that nobody will want to break our application on purpose….

Bingo for meetings – part 3 – finalizing the “Create Meeting” scenario

Bingo

Nr	Link
1	Create meeting
2	Create Tests
3	Finalize Create meeting
4	Sharing meeting
5	Keep Score
6	Add obsolete
7	Finalizing obsolete
8	End meeting
9	Dockerize tests
10	Azure CI tests
11	Yarn workspaces
12	CLI
13	Intermezzo - CLI improvements
14	typescript compile run with node
15	NestJS ,swagger and create a meeting
16	Finalizing API
17	Intermezzo - jest vs jasmine error
18	Refactor WebAPI and test service
19	Heroku Deploy NestJs
20	Angular
21	Deploy Angular to GitHub
22	WebAPI and Web
23	Documentation
24	Documentation of the code
25	Conclusions

In the “Create Meeting” scenario it was something that we have passed : ” application generates an unique Id that I can access the bingo cards ( state : not checked) for that meeting ” ( see https://github.com/alexandru360/PresentationBingoCards/projects/1#card-24165690 )
How we can emulate this ? Obviously, the meeting starts with a set of cards – but how about participants ? Do they have the same set of cards and check them ( bingo ) ?

There are some possible things to be programmed here:

1. The meeting have the unique set of cards and the dictionary of .

2. Every participant , when joining the meeting, have a copy ( by reference ) of the meeting cards and an array to see what is checked

3. Every card keep an array of participants that shows what participant have checked the card.

Guess what is easiear to implement ?

However, we have put a function on the meeting

public AllUnchecked(): boolean{
        return (this.Cards.filter(it=>it.IsChecked()).length === 0);
    }

and a test to ensure that, when creating a meeting, the function returns false.

So now the first scenario is done !

( On a personal note, I see that yarn is better than npm )

Bingo for meetings–part 2–working at tests

Bingo

Nr	Link
1	Create meeting
2	Create Tests
3	Finalize Create meeting
4	Sharing meeting
5	Keep Score
6	Add obsolete
7	Finalizing obsolete
8	End meeting
9	Dockerize tests
10	Azure CI tests
11	Yarn workspaces
12	CLI
13	Intermezzo - CLI improvements
14	typescript compile run with node
15	NestJS ,swagger and create a meeting
16	Finalizing API
17	Intermezzo - jest vs jasmine error
18	Refactor WebAPI and test service
19	Heroku Deploy NestJs
20	Angular
21	Deploy Angular to GitHub
22	WebAPI and Web
23	Documentation
24	Documentation of the code
25	Conclusions

So now because we have created the objects and a function to create meetings, we do create some tests. We decided to work with JEST.

Steps:

We read many tutorials (https://medium.com/@mtiller/debugging-with-typescript-jest-ts-jest-and-visual-studio-code-ef9ca8644132 , https://rjzaworski.com/2016/12/testing-typescript-with-jest , https://github.com/facebook/jest/tree/master/examples/typescript , https://amenallah.com/node-js-typescript-jest-starter/ , https://basarat.gitbooks.io/typescript/docs/testing/jest.html , https://dev.to/muhajirdev/unit-testing-with-typescript-and-jest-2gln )
We solve many errors ( forgetting put “ export default class “ , “ jest unexpected token import “ , jest.config.json as opposed to jest.config.js
Read jest expect documentation from https://jestjs.io/docs/en/expect.html#not
We finally wrote 2 tests in order to verify meeting creation and run with npm test

import MeetingsFactory from '../MeetingsFactory';
 
import Meeting from '../meeting';
 
describe('Meetings creation', () => {
 
it('a meeting should have been created properly', () => {
 
const mf=new MeetingsFactory();
 
const m1=mf.CreateMeeting("andrei","first meeting");
 
expect(m1.Name).toBe("first meeting");
 
expect(m1.Participants.length).toBe(1);
 
expect(m1.Participants[0].Name).toBe("andrei");
 
})
 
it('two meeting have different ids', () => {
 
const mf=new MeetingsFactory();
 
const m1=mf.CreateMeeting("andrei","first meeting");
 
const m2=mf.CreateMeeting("andrei","first meeting");
 
expect(m1.Id).not.toBe(m2.Id);
 
})
 
})

And with this we just verify first use case

Create Meeting Bingo:

As a user, I want to create a new meeting bingo: I use an username and meeting name and the application generates an unique Id that I can access the bingo cards ( state : not checked) for that meeting

And not even the whole( we do not have the cards , not the state for the cards!)

New project: Bingo for meetings–part 1

Bingo

Nr	Link
1	Create meeting
2	Create Tests
3	Finalize Create meeting
4	Sharing meeting
5	Keep Score
6	Add obsolete
7	Finalizing obsolete
8	End meeting
9	Dockerize tests
10	Azure CI tests
11	Yarn workspaces
12	CLI
13	Intermezzo - CLI improvements
14	typescript compile run with node
15	NestJS ,swagger and create a meeting
16	Finalizing API
17	Intermezzo - jest vs jasmine error
18	Refactor WebAPI and test service
19	Heroku Deploy NestJs
20	Angular
21	Deploy Angular to GitHub
22	WebAPI and Web
23	Documentation
24	Documentation of the code
25	Conclusions

I have decided to start a new project. The name is “Bingo for meetings”. What it does: Every time in a meeting that a participant hears a phrase (like “ Hi, can you hear me?” or “ can everyone see my screen?” or others …) he can check one of the cards. In the final you can see for the meeting how many cards you have checked.

I am doing the project with Alexandru Badita (http://alexandru360.blogspot.com/) . We agreed to be in ONLY in TypeScript .

We are doing at Starbucks the pair programming and exchange ideas. Total time: 1 hour

In the first meeting we have put the specifications at https://github.com/alexandru360/PresentationBingoCards/projects/1

Create Meeting Bingo:

As a user, I want to create a new meeting bingo: I use an username and meeting name and the application generates an unique Id that I can access the bingo cards ( state : not checked) for that meeting

Share Meeting Bingo:

As a User, I can receive the meeting Id( url) . When going to this url , I can ( optionally) enter my name and check cards

Checking cards:
A total score will be displayed when checking / unchecking

EndMeeting:
The score of how many cards/ what cards were checked will be available 1 hour and 5 minutes

Meeting Obsolete:
The meeting is available for 35 minutes. After that, meeting is not available anymore.

Also, we have created the classes Meeting, Participant, Also, we have created a MeetingsFactory that can create a Meeting.

You can fist the result of our code at https://github.com/alexandru360/PresentationBingoCards/releases/tag/firstMeeting

Category: bingo

Bingo for meetings– working at sharing meeting with others–part 4

Bingo

Bingo for meetings – part 3 – finalizing the “Create Meeting” scenario

Bingo

Bingo for meetings–part 2–working at tests

Bingo

New project: Bingo for meetings–part 1

Bingo

Andrei Ignat weekly software news(mostly .NET)