FiberFold code coverage

[3dphoto]

We'll have lots of FiberFold ideas integrated over time, I won't be able to keep up with all that is going on internally we would need a QA team at some point. Unless you have code coverage for FiberFold:

An Overview of JavaScript Testing in 2018

• UI Tests- (A.K.A Functional Tests) Testing scenarios on the product itself, by controlling the browser or the website, regardless of the internal structure to ensure expected behavior.

An Overview of JavaScript Testing in 2017

• Unit Tests- Testing of individual functions or classes by mocking input and making sure the output is as expected.

• Integration Tests- Testing several modules to ensure they work together as expected.

  • Bottom-up integration- This testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds.
  • Top-down integration- This testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing. The process concludes with multiple tests of the complete application, preferably in scenarios designed to mimic those it will encounter in customers' computers, systems and network.

• Functional Tests- Testing a scenario on the product itself (on the browser, for example) regardless of the internal structure to ensure expected behavior.

• System Testing- This is the next level in the testing and tests the system as a whole. Once all the components are integrated, the application as a whole is tested rigorously to see that it meets Quality Standards. This type of testing is performed by a specialized testing team.

• Regression Testing- Whenever a change in a software application is made it is quite possible that other areas within the application have been affected by this change. To verify that a fixed bug hasn't resulted in another functionality or business rule violation is Regression testing. The intent of Regression testing is to ensure that a change, such as a bug fix did not result in another fault being uncovered in the application.

• Acceptance Testing- This is arguably the most importance type of testing as it is conducted by the Quality Assurance Team who will gauge whether the application meets the intended specifications and satisfies the client.s requirements. The QA team will have a set of pre written scenarios and Test Cases that will be used to test the application.

  • Alpha Testing- This test is the first stage of testing and will be performed amongst the teams (developer and QA teams). Unit testing, integration testing and system testing when combined are known as alpha testing. The Application will be tested on machines with the lowest specification to test loading times and any latency problems.
  • Beta Testing- This test is performed after Alpha testing has been successfully performed. In beta testing a sample of the intended audience tests the application. Beta testing is also known as pre-release testing. Beta test versions of software are ideally distributed to a wide audience on the Web, partly to give the program a "real-world" test and partly to provide a preview of the next release.

[s1pierro]

I'm trying to include a few of that. By using try catch some prompt is done, and finally erased is no errors occurs. here I volontary include one :

But you are right ! More automated tests would be so usefull. They will be added at the RC state. The app will be migrated on a server that run Php to collect data about Terminals. In a large way. as echiquierJs does a little bit.

[3dphoto]

WOW this is so awesome to see happening!