About the conference: ReactFoo is a single-day React conference by HasGeek.
We’ll be annoucing the theme shortly
We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15-minute talks.
Hands-on Workshop sessions, 3 and 6 hour duration.
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.
We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.
You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.
A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.
There is only one speaker per session. Entry to the conference is free for selected speakers. As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable: two international travel and accommodation grants, three domestic travel and accommodation grants. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer). Speaker travel grants will be given in order of preference to students, women, persons of non-binary genders, and individuals for Asia and Africa first.
##Commitment to open source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a “sponsored session”.
Deadline for submitting proposals: 23 August 2017
**Conference date: ** 14 September 2017
For more information about speaking proposals, tickets and sponsorships, contact firstname.lastname@example.org or call +91 76763 32020.
Please note, we will not evaluate proposals that do not have a slide deck and a video in them.
Unit Testing React Applications
Testing is like working out. Everyone knows it’s good for you but very few of us do it.
Testing frontend applications is very different from testing their backend counterparts. Hence, we consider it to be difficult and shy away from it.
The most common dilemmas we face when it comes to frontend testing are: a) where to start and b) how to test. This talk aims to instil a testing mindset while providing a deep insight into frontend testing and how to go about it the right way.
I will be talking about the AAA pattern which makes it easy to write tests for anything. AAA stands for Arrange, Act, Assert. All unit tests consist of these 3 stages. Writing tests becomes easy when you are able to break the test down into these stages.
Maintaining tests is another important aspect often ignored while testing. We need to set up processes, such as pre merge test runs,that ensure that the corresponding tests are always updated after every code change.
When you have a good grasp of writing tests for frontend applications, testing applications built using React and Redux can be easy because of the declarative style in which they’re written.
The talk will be focused on how to test applications built with React and Redux and will cover the following areas
- Need for testing
- Testing framework setup
- AAA pattern to write tests - Arrange, Act, Assert
- Testing components
- Testing action creators
- Testing reducers
- Maintaining tests
- When testing is an overkill
The talk is aimed at people who already have some experience building applications in React.
I am a UI engineer at Flipkart and as a part of the team that rebuilt the desktop website from the ground up, I have set up the testing framework and processes for the Flipkart desktop website, as well as for other projects within the company. I am a great believer in good and thorough testing and think that better testing always leads to better software.