Join Firebird!

Join Firebird Foundation to support Firebird SQL development and receive multiple bonuses

Follow Us

Select your media preference

Newsletter

Subscribe to Firebird’s Newsletter to receive the latest news

Developer's Report: QA Stress Testing & Development
April to August 2021

August 2021
  • Created / modified QA tests for ~20 tracker tickets
  • FB QA, new framework: learned documentation, ran first probe scripts, checked avaliable features of the 'firebird.driver' package
  • Replication: continued work with prototype of test that applies DDL of OLTP-EMUL and verify it on the replica db
July 2021
  • Created / modified QA tests for ~30 tracker tickets
  • Found / reported bugs: #6884
  • Implemented test that repeats all DDL actions of OLTP-EMUL
  • Created auxiliary script for memory monitoring during fbtest work
June 2021
  • Created / modified QA tests for ~20 tracker tickets
  • Found / reported bugs: #6854, #6861, #6862, #6868, #6869, #6873, #6874, #6875, #6877
  • Refactored QA_rundaily.bat to support replication
  • Reported missing plugin\engine13.pdb in Windows v5 snapshots
May 2021
  • Created / modified QA tests for ~50 tracker tickets
  • Found / reported bugs: #6790, #6802, #6807, #6821, #6829, #6831
  • Re-enabled tests for CORE-3058 and CORE-1544 for regular runs
  • First test runs with pytest and new firebird-driver
  • Created SQL-prototype for covering all possible cases for #3106 and #3810 (optimization of NULLs search in indexes)
  • Found problems related to recently committed #6748
  • Discussed with P. Cisar the missing information in the new pytest system
  • Lot of changes in the qa-rundaily and fbt-cross-report scripts because new major FB version (5.x) appeared
  • Scratch for design HTML page with overall results for all FB versions and OS
April 2021
  • Created / modified QA tests for ~60 tracker tickets
  • Found / reported bugs: CORE-6531, CORE-6532, CORE-6535, #6821
  • Checked ability to establish connection using INET, WNET and XNET from client 3.0.7 to server 4.0 (and vice versa)
  • Multiple QA runs, regressions are reported to developers
  • Found problem with obtaining info from mon$ tables when user has non-ascii name

Pavel Zotov
Moscow, Russian Federation
 
April to August 2021

August 2021
  • Created / modified QA tests for ~20 tracker tickets
  • FB QA, new framework: learned documentation, ran first probe scripts, checked avaliable features of the 'firebird.driver' package
  • Replication: continued work with prototype of test that applies DDL of OLTP-EMUL and verify it on the replica db
July 2021
  • Created / modified QA tests for ~30 tracker tickets
  • Found / reported bugs: #6884
  • Implemented test that repeats all DDL actions of OLTP-EMUL
  • Created auxiliary script for memory monitoring during fbtest work
June 2021
  • Created / modified QA tests for ~20 tracker tickets
  • Found / reported bugs: #6854, #6861, #6862, #6868, #6869, #6873, #6874, #6875, #6877
  • Refactored QA_rundaily.bat to support replication
  • Reported missing plugin\engine13.pdb in Windows v5 snapshots
May 2021
  • Created / modified QA tests for ~50 tracker tickets
  • Found / reported bugs: #6790, #6802, #6807, #6821, #6829, #6831
  • Re-enabled tests for CORE-3058 and CORE-1544 for regular runs
  • First test runs with pytest and new firebird-driver
  • Created SQL-prototype for covering all possible cases for #3106 and #3810 (optimization of NULLs search in indexes)
  • Found problems related to recently committed #6748
  • Discussed with P. Cisar the missing information in the new pytest system
  • Lot of changes in the qa-rundaily and fbt-cross-report scripts because new major FB version (5.x) appeared
  • Scratch for design HTML page with overall results for all FB versions and OS
April 2021
  • Created / modified QA tests for ~60 tracker tickets
  • Found / reported bugs: CORE-6531, CORE-6532, CORE-6535, #6821
  • Checked ability to establish connection using INET, WNET and XNET from client 3.0.7 to server 4.0 (and vice versa)
  • Multiple QA runs, regressions are reported to developers
  • Found problem with obtaining info from mon$ tables when user has non-ascii name

Pavel Zotov
Moscow, Russian Federation