Labs/Bespin/Testing

Testing

There are many forms of testing, and this will encapsulate the various types.

• Unit Testing: Low level code testing
• Test Plan: Manual testing to help make sure Bespin is running well
• Functional Testing: High level automated functional tests

Areas of Testing

The areas of testing that we want to focus on first are:

• Simple Syntax Errors: As soon as I bring suck in a new file I want to run a test that makes sure that there are no JavaScript syntax errors.

• Regressions: We want to get enough code coverage so we don't run into many regressions as new features are added. This means lots of unit testing!

• Performance: We need to be laser focused on the UI latency of the application. This can be hard to test, but we want to do things such as measuring the aggregate time of paint() and running tests across the browsers to see differences.