Open andreasohlund opened 8 years ago
@dvdstelt is working on something that is related to this as well
@andreasohlund duplicate with #3 ?
@WojcikMike Stability vs Performance :smile:
I kept them separate on purpose, not against merging if needed
@dvdstelt Want to chat about this tomorrow morning your time? I'd like to help out with this.
@Particular/transport-maintainers should we include https://github.com/Particular/NServiceBus.AzureServiceBus/issues/106 into this one and close it?
@andreasohlund that one is not an automated test, but endurance test to run for a long period of time to catch anything we didn't accommodate for. Also, 106 is only for one of the topologies. There's a second issue (https://github.com/Particular/NServiceBus.AzureServiceBus/issues/76) that's being worked on.
but endurance test to run for a long period of time to catch anything we didn't accommodate for
That was my intention with this issue. Ie to run tests for longer periods of time to make sure we're stable?
As discussed today this is a prio for us. @gbiellem are you ok with putting you as the task force lead?
who else can join the taskforce?
I can join, but need to first make sure that our outbox tests got merged in
@andreasohlund I'd be happy to participate, don't know about leading it. I'd suggest pulling in @johnsimons as well, he's done this before so I assume he'd be across what you want out of this effort.
@johnsimons do you want to join this?
@WilliamBZA pretty sure you wanted in as well?
If yes that I'll leave it up to the 3 of you to decide on a lead
@andreasohlund Definitely want in!
As @andreasohlund commented in #3 , performance has higher priority than stability tests. Because of that this issue will be done after performance tests are done, as there is a big probability of reusing parts of the same code base.
Because of that fact @gbiellem @johnsimons are you interested and have time please comment on #3
@gbiellem Since i am also working on this for ASB I will join.
I closed https://github.com/Particular/NServiceBus.AzureServiceBus/issues/76 and https://github.com/Particular/NServiceBus.AzureServiceBus/issues/106 and updated the description of this Issue to indicate they include those tests within this scope as well.
https://github.com/Particular/NServiceBus.AzureServiceBus/issues/76 has some code already that will need to be migrated to this issue when it has the green light to proceed.
@WilliamBZA @ramonsmits would this be suitable to start now in order to lay the foundation for testing needed in order to get us into RC status?
Perhaps we can scope this down to a tracer bullet:
I think it would, but there will probably also be a few side issues for additional fixing/testing, as discussed this morning. But this can run in parallel
Given the amount of automated testing done around performance and the planned testing for SC @Particular/tf-v6-launch-plat-dev has decided to remove this from v6 scope for now
Taskforce:
We need to run stability tests for v6 transports and persistence. I have a hunch that we can reuse the code and infra from the outbox tests?
cc @gbiellem @WilliamBZA @WojcikMike @Particular/transport-maintainers @Particular/persistence-maintainers