Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
P
Production Test Suite - base
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Projects
  • Production Test Suite - base
  • Wiki
  • Cleanuptodo

Cleanuptodo

Last edited by Projects Aug 13, 2014
Page history

Clean-up TODO list

The following mainly concerns the fmc-adc, fmc-tdc and spec projects.

General idea

  1. Split test project in two, common (pts project) and board specific (-tst project)
  2. Keep gnurabbit.
    -> move common test code to pts-tmp
    -> move specific test code to <prj_name>-tst
    -> move hdl code to <prj_name>-gw
  3. Define a new generic API and implement library.
  4. Port tests to new library.

pts common code

  • Add test example.

fmc-adc-tst

  • move to new API.

pts fmc-tdc

  • hdl test source code to gateware sub-project.
  • split in two parts.
  • Adapt tests to common classes
    -> at least eeprom_24AA64
    -> check others
  • calibr_box.py and cp210x_eeprom.py are specific to tdc, should be placed in fmc-tdc-tst (not in common).
  • move to new API.

SPEC

  • hdl test source code to gateware sub-project.
  • split in two parts.
  • move to new API.

pts fmc-fdelay

  • split in two parts.
  • ?
Clone repository
  • Home
  • Cleanuptodo
  • Faq
  • Testapi
More Pages

New Wiki Page

Tip: You can specify the full path for the new file. We will automatically create any missing directories.