Sorry guys I've been traveling and haven't had the chance to start the discussions on this. We more or less have our requirements as gathered at the summit I'll try to send them out today so we can begin discussing a roadmap.
Brian On Monday, November 3, 2014, Joshua Blatt <bla...@yahoo-inc.com.invalid> wrote: > Good feedback... I'll address that > > On Monday, November 3, 2014 9:56 AM, James Peach <jpe...@apache.org > <javascript:;>> wrote: > > > > > On Nov 3, 2014, at 8:46 AM, Joshua Blatt <bla...@yahoo-inc.com.INVALID> > wrote: > > > > Hi guys, > > The clouds have parted and I have time to return to the functional test > framework. I'm thinking for starters I'll transcode the nodejs impl at > apache/trafficserver into python, then see how well it fares reproducing a > few open issues we know about. If anyone would like to discuss this, > please let me know. > > Hi Josh, > > I did review your prototype on github. The main thing that struck me was > the duplication of entire ATS configurations. IMHO this is a non-starter. > Tests should either declare the settings they need, or use convenience API > to make (synchronous) configuration changes. In general, we should prefer > succinct, declarative configurations for tests. > > > Thanks, > > Josh > > > > > > | | > > | | | | | | | | > > | apache/trafficserverHi guys, This is a first stab at a functional test > framework. My intention is to stimulate discussion for the test framework > talk at the ATS Summit. I won't be shat... | > > | | > > | View on github.com | Preview by Yahoo | > > | | > > | | > > > > > > >
