10.19.2023 SLIM Developers Tag Up

Announcements

• November meetings

Agenda / Notes

• Continuous Testing ticket @yunks128: https://github.com/NASA-AMMOS/slim/issues/110
  • @riverma developed a standardized template we could augment for this ticket
  • Working / progress on tool recommendation
    • Feedback from @jpl-jengelke et al: keep tools relevant not necessary fully comprehensive for all use cases.
    • Example (Unity) see repos and study the tech / language makeup here
  • Presentation made to Unity project, feedback:
    • Roles for testers did not include usability testing / user interface testing - how does this fit into our model? Does it need to?
    • Feedback on not being enough personnel to implement all tools recommended by SLIM for CT
      • Need to come up with a curated, common sub-set of tools for all projects and rank their importance
    • Some tools are not relevant given lack of maturity of project - we may need to wait for including tools like integration testing for example
    • Feedback that the most critical / important CT test phases from a project perspective are: Security, VnV, InT. We should prioritize these.
    • Consider the license agreements for tools that we are recommending - even though it's open source, the tool may have a cost associated.
    • Concurrence that iteration of test implementation is very important - can't get it right the first time
  • Next Steps
    • Identify a curated set of common tools that are most important to SLIM projects (research / surveys, etc.)
    • Review and augment template with feedback as well as sections that have not yet been included but you feel should (e.g. iteration).
    • Consider creating a draft PR to progress your work
• Infusion @jpl-jengelke
  • Ongoing infusion
  • Leaderboard boards can be posted internally institutionally (TBD) and on NASA-AMMOS/ GitHub (TBD)
  • Next Steps
    • Infusion of all Git Essentials SLIM recommendations (other than README's) institutionally by next tag-up