Hi Craig, > I understand that once tooling has transitioned the whimsy agenda to tooling > agenda, one of their next projects will be the secretary workbench.
Yes, > It will be valuable for the primary engineers on the tooling workbench to > have a test setup, and to be able to see the whimsy workbench in action. Yes, this will be valuable one aspect of having a test setup is proper control of PII alone with having a test setup. How do you test the Whimsy workbench? > It will be in our best interest to make this happen. And it won't happen > without taking action. Agreed. > Tossing out ideas here. > > Add some tooling test users who can work on the existing whimsy workbench > with some test ICLA, CCLA, etc. forms. > > Set up a new VM with the existing whimsy workbench with an entire set of test > environments. This would have to include some test LDAP, test svn repos, test > email etc. > > TBH I don't even know who on the tooling team will be assigned to the > workbench task and who might need access to to the existing workbench. For now, it’s enough to know that the whole Tooling Team should be involved. Please use [email protected] Let’s have a discussion about the proper test environment. Given the need for test LDAP and SVN along with a special mailing lists and email addresses, standing up a Whimsy test environment on the same host as the Dev Tooling environment would be the proper approach. We do have the production puppet configurations from Infra. Please describe how the current tool is developed and tested. Best, Dave > > Craig L Russell > [email protected] >
