Improve p5.Table.js unit tests

[diyaayay]

Increasing Access

Currently p5.Table.js has test suites only for loading a table in loadTable.js and saving a table saveTable.js . However, there are areas with missing test cases for eg: Modifying a table (addRow, removeRow, etc. ) or building a table from scratch which would increase the code coverage of p5.Table.js , indicated below:

p5.js uses mocha, mocha-chrome, chai.js assert, and expect for its unit tests.
There are separate files for different test suites, loadTable.js and saveTable.js
Maybe the modifyTable.js can be another file that can be added to the unit test or the modify table tests can be written in an existing file.

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build Process
• Unit Testing
• Internalization
• Friendly Errors
• Other (specify if possible)

Feature enhancement details

• Increasing the code coverage for p5.Table.js
• writing new unit tests using mocha, chai.js, etc.
• Tweaking into more test cases for correct format of values entered/modified in the table.

[welcome]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you!

[diyaayay]

I would like to work on this issue.
Would be grateful if a reviewer can confirm so that I can start working in this.

[lindapaiste]

@davepagurek FYI I suggested this based on looking at the coverage report. If there’s any area that’s more of a priority then feel free to suggest!

[davepagurek]

@limzykenneth mentioned possibly deprecating p5.Table in a 2.0 release in favour of native js data types. Is that still the plan?

If so, it might be a better use of effort to tackle something else -- looking at codecov to find p5.Table was a great idea, is there anything else that comes up? I don't think anything else was considered for deprecation, so improved coverage for other parts of the codebase is appreciated!

[limzykenneth]

The plan is to consider deprecating p5.Table (removing entirely or made into addon library) for 2.0. I'll publish the full proposal for 2.0 in a couple days and we can discuss the future plan for this then.