FIP Development

Owned by Eric Butz
Feb 01, 2022
1 min read

Core chain and contract development

  • Development of Foundation-led FIPs

QA of core chain and contracts

  • QA for all FIPs

fio and fio.contracts automated testing

fio and fio.contract QA is covered by the fio.test javascript test harness. New automated tests are created for every new action, endpoint and feature added to the protocol. Full regression tests are run for every release.

The current process for developing automated tests generally follows:

  • FIP/requirements are defined by product team

  • Product team publishes initial test cases

  • Test cases are enhanced by development and QA teams

  • FIO development creates initial tests as a template

  • FIO QA completes full automated tests

KPIs

Task

KPIs

Task

KPIs

Code delivery

  • Minor FIPs delivered to chain within 3 months

  • Maintain code delivery dashboard

QA

  • Automated tests for all new actions and endpoints

  • Maintain QA dashboard

    • summary of test coverage

    • tests in development with estimated release dates

  • Testnet testing completed within 2 hours of new releases

  • Mainnet testing completed within 2 hours of new releases

Release management

  • Timely delivery of Devnet, Testnet, and Mainnet releases. TBD on this process.

  • Maintain Release dashboard

    • Release pipeline

    • Release history and versioning

Documentation and knowledge sharing

  • Update Devhub with new feature info within 2 weeks of release

FIO Chain and contract security

  • Maintain security playbook

  •  

EOSIO compatibility and community support

 

Developer outreach and community building