Skip to main content

Introduction to Code Base for easyform

So its been the end of community bonding period and I have been looking into the code base for which I will be working for this summer's project. Collective.easyform, A project for Plone which helps in create forms for plone using dexterity content type. So the project mainly focuses on Improving this add-on to work for properly for Plone5.

Current Status of collective easyforms :-



Wooh!! It's breaking and failing at lot of the parts. So right now the project is failing for tests and one of the main task of the project is the improve tests to make them work for project. Improving tests help us in tracking the future changes of the project so that we can see if new things/features are working properly in the code.

Work done till now :-

So till now I have done the setup for the project and did one feature correction, the basic mailer_template which is the default one is not able to render properly and it was showing error, so to make it fix everytime, we have to correct the mailer_template code through the web to make it work.

Also I have came to few new functionality in easyform that are different from PFG (Plone FormGen, archetype way to create forms). The main change is earlier in PFG the receipt address for mailer configuration is taken from site's owner mailer address as a default but in easyform, one have to configure the email address to make the mailer thing work. This is also a good feature as one should not depend on site's owner email address for sending mails.

So this is work till now, soon I will write about how I have improved the tests for easyforms. I am working on it and have done a great progress on that too.

Cheers!!



Comments

Popular posts from this blog

Summarizing Summer

It was a great pleasure to work with great coders/developers at Plone Foundation and learning a lot from them during the course of the program. This blog is about summarizing the whole work I have done during this summer under Google summer of code 2016 under Plone Foundation. So my project mainly focuses on improving forms in plone for dexterity. We already have forms in plone for archetype. So there is a project named collective.easyform which basically provide forms for Plone as dexterity contenttype. The main focus of the project was to improve that code base. Make this stable for plone 5.0 and above. Make all the test cases passing for the code base. Try to cover tests as much as possible code base. Also implement functionalities for fields/actions of the forms in correct place. Make the plone more user friendly. Finally for users who want to migrate their already present forms in Plone Form Gen (PFG) which is archetype to easyforms which are dexterity based forms Plone. This w

Testing the transform

Hello everyone, now the transform for filtering html is ready and the main task is to test the transform. For that purpose I have set up the whole test environment for my add-on using testing.py for unit tests and robot tests. After setting up the environment, now its time to first write unit test for transform that we have just created to check if they are all passing and the transform is working properly or not. For creating unit test I first created test class and in that class I just call the convert function that we have created in the transform and give the input as a data stream and pass it to convert function and then get the output as required. After writing few simple test cases like 30-35 then just ran these test cases and they ran successfully. Test cases ran successfully locally :- Travis is also happy ;) Yayayay!!! Finally test cases were passing so its like a milestone for the project and its completed. The PR got merged and things working good as expect