Available!

We are happy to announce that DevRiot for Visual Studio 200X(Beta) is available for downloading at:

http://efekctive.com/beta_public/

The documentation can be found at:

http://efekctive.com/docs/

Don't forget you will need a working email address, a working internet connection, and a SQL Server instance available to install and use DevRiot (the email address is required during setup only)

We hope you find it useful and worth the time to try it! If you have any questions please contact us at this address: beta at efekctive dot com.

Documented

The documentation is "done". It needs editing to polish my written "spanglish". The setup needs changing to avoid a random identification failure while installing a final round of "monkey testing" and beta should be ready to go!

Wiking!!

For the last few days we have been putting together a simple documentation for this beta. It can be found at: http://www dot efekctive dot com/docs.

Mild and off-target...

After a harmless hack attempt at the wrong site, it was suggested by my isp to harden the site logic. We did so it is robust enough to avoid the easy gotchas, we believe.

Now off to put a little documentation together with the previous images and posts and it should be ready for the public to break...

DevRiot Beta is wating for deployment...

We fixed the nested generics problems. It looks good enough to let people really find its problems.

This leaves DevRiot beta ready to be used once the deployer method is ready. Will be off the grid on a 2-week friends & family & surfing trip. A break is called for.

1,600 T

I have been trying to squeeze more than 1,600 concurrent threads out the engine without changing any settings. No luck. Obviously, it will need a closer, slower look and better tools. Still 1,600 is a number that can be useful, specially when one invests 30 seconds or less to create, use, and harvest.

Pit Stop!!

From time to time things deadlock, etc. Well, for those occasions DevRiot lets you deal with them seamlessly...

Progress one thread at a time...

Arrays and Dynamic fixtures seem to be stable. A couple of bugs that we'll need to get back to but nothing to keep us from moving on to threading/Load & Stress...

The octopuss

Recompiling load & stress tests is taking some bug-fixing effort. Working on it :-}

Time To Change...

Well after fiddling around with the load/stress engine + 1,600 threads/users for a while, I think it makes more sense to let users set the TTL per test.

It is easier for the user to set it according to their knowledge of the code than use any predefined formula.

It also becomes part of the verification data of the test which should be useful.