Automated testing

[ifedapoolarewaju]

Automated testing

[ifedapoolarewaju]

Hi, I am really glad that you would like to take this up! 😊 Regarding the suggestions, I would go with Travis CI since we already previously have a .travis.yml file in the code. However, I am ok with using the other libraries you suggested for writing the tests (though I haven’t used any of them before now).

…

On 25 Dec 2018, at 5:29 PM, Alex ***@***.***> wrote: @ifedapoolarewaju I'm interested in taking this. A few thoughts that you might want to review before I start working on things: There's going to be a need for CI (continuous integration) to make this work. GitHub has a large range of tools to pick from but I'd go for one of the most prominent Travis CI is free for open-source projects, so is Cirrus CI both support JS natively, but the latter supports TS which, should it ever happen, makes rewriting tests easier. I don't have any experience in any of the two though, so I guess setting up either is fine and ultimately your decision. We need to decide on a test library, a framework eventually and maybe also add mocking libraries I recommend Intern for the library and framework as well as Stryker Mutator for mutation testing @Ghous290 @jacklin2 @NoraAlbab10 This is an issue where the author asks for help with adding a new feature. GitHub has an issue tracker for a reason and it also has a search function for a reason. If the app doesn't work for you, you're not able to login or whatever it is, first search through open issues (Hint: There's already many of them open) and if you can't find the one best suited for your case, open a new one. Don't revive old issues that might contain otherwise useful information for other people to see but not notice because it's hidden behind 200 comments saying "help me". Even though it's not bad in itself, please try paying more attention to that in the future. Some developers don't like "nagging" and ignore you for the rest of your lives even if the next issue is well made and nobody wants that. So here's some good reads on Issue etiquette you might want to follow to make a better issue out of it next time. http://www.defmacro.org/2013/04/03/issue-etiquette.html https://ben.balter.com/2014/11/06/rules-of-communicating-at-github/ https://github.com/rstacruz/collaborative-etiquette/blob/master/README.md#top https://upthemes.com/blog/2014/02/writing-useful-github-issues/ (beware, not all of us like screenshots) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[NoraAlbab10]

the app stopped working

[jacklin2]

I was trying to login the app but it didn't work and it said that a code was sent to my email which actually wasn't sent

[Ghous290]

I was trying to login the app but it didn't work and it said that a code was sent to my email which actually wasn't sent same problem........ help me

[curtisy1]

@ifedapoolarewaju I'm interested in taking this. A few thoughts that you might want to review before I start working on things:

1. There's going to be a need for CI (continuous integration) to make this work. GitHub has a large range of tools to pick from but I'd go for one of the most prominent Travis CI is free for open-source projects, so is Cirrus CI both support JS natively, but the latter supports TS which, should it ever happen, makes rewriting tests easier. I don't have any experience in any of the two though, so I guess setting up either is fine and ultimately your decision.
2. We need to decide on a test library, a framework eventually and maybe also add mocking libraries I recommend Intern for the library and framework as well as Stryker Mutator for mutation testing

@Ghous290 @jacklin2 @NoraAlbab10 This is an issue where the author asks for help with adding a new feature. GitHub has an issue tracker for a reason and it also has a search function for a reason. If the app doesn't work for you, you're not able to login or whatever it is, first search through open issues (Hint: There's already many of them open) and if you can't find the one best suited for your case, open a new one. Don't revive old issues that might contain otherwise useful information for other people to see but not notice because it's hidden behind 200 comments saying "help me". Even though it's not bad in itself, please try paying more attention to that in the future. Some developers don't like "nagging" and ignore you for the rest of your lives even if the next issue is well made and nobody wants that. So here's some good reads on Issue etiquette you might want to follow to make a better issue out of it next time.
http://www.defmacro.org/2013/04/03/issue-etiquette.html
https://ben.balter.com/2014/11/06/rules-of-communicating-at-github/
https://github.com/rstacruz/collaborative-etiquette/blob/master/README.md#top
https://upthemes.com/blog/2014/02/writing-useful-github-issues/ (beware, not all of us like screenshots)

[curtisy1]

Hi, I am really glad that you would like to take this up! blush Regarding the suggestions, I would go with Travis CI since we already previously have a .travis.yml file in the code. However, I am ok with using the other libraries you suggested for writing the tests (though I haven’t used any of them before now).

Alright, I'll start working on it and submit a WIP PR once I got the first tests rolling 😄