One of the interesting challenges that we have with RavenDB is the number and duration of our tests. In particular, we current have over three thousands tests, and they take hours to run. We are doing a lot of stuff there “let us insert million docs, write a map/reduce index, query on that, then do a mass update, see what happens”, etc. We are also doing a lot of stuff that really can’t be emulated easily. If I’m testing replication for a non existent target, I need to check that actual behavior, etc. Oh, and we’re probably doing silly stuff in
there, too. In order to try to increase our feedback cycle times, I made some modifications to xUnit. It is now going to record the test duration of the tests, the results look like that: You can see that Troy is taking too long. In fact, there is a bug that those tests currently expose that result in a timeout exception, that is why they take so long. But this is just to demonstrate the issue. The real power here is that we also use this when decided how to run the tests. We are simply sorting them by how long they...(Read whole news on source site)
If you want to display tick marks on a Slider, you set the TickPlacement property to indicate where you want the tick marks to appear: None - don’t display tick marks (default) BottomRight - display below horizontal Slider, to the right of vertical Slider TopLeft – display above horizontal Slider, to the left of vertical Slider Both […]
Because RavenDB is a database, a lot of the tests we have to run are pretty long. For example, we need to touch the disk a lot, and we have a lot of networked tests. that means that running this test suite can take a while. But the default information we get is pretty lousy. Just the test count and that is it. But when a test hang, and they do if we have bugs, it make it very hard to figure out where the culprit is. So we forked xunit and added a tiny feature to the console runner:
Software Visual Studio Online early adoption period extended! - The Visual Studio Team announce the extension of the early adopters period for Visual Studio Online, now extended to 7th May 2014. Visual Studio 2013 Update 2 and Web Essentials - Mads Kristensen discusses the Visual Studio 2013 Update 2 CTP2 release and how it effects Web [...]
Originally posted on: http://geekswithblogs.net/TATWORTH/archive/2014/03/03/apress-deal-of-the-day---3mar2014---asp.net-mvc.aspx Today's $10 deal of the day from APress at http://www.apress.com/9781430249771 is http://www.apress.com/9781430249771 "Build cutting-edge REST services using ASP.NET MVC 4 and the Web API. Learn how to design, implement and deploy CRUD-based services quickly and efficiently in this concise guide."
Last week, I re-learnt something which, according to me, is a little counter-intuitive. I was studying read-only databases out of academic interest and noticed something interesting: When a database is marked as Read-only, the underlying file/file-groups are not marked Read-only. Here’s a simple test wherein we: Create a test database with multiple file-groups (the test works equally well with a single file-group) Set the database to READ_ONLY Check the file-group properties USE master; GO --Create the test database CREATE DATABASE ReadOnlyDB ON PRIMARY
(Name=ReadOnlyDB_Primary, FileName='C:\Databases\SQL2012\ReadOnlyDB_Primary.mdf' ), FILEGROUP SecondaryFG (Name=ReadOnlyDB_Secondary, FileName='C:\Databases\SQL2012\ReadOnlyDB_Secondary.ndf' ) LOG ON (Name=ReadOnlyDB_Log, FileName='C:\Databases\SQL2012\ReadOnlyDB_Log.ldf' ); GO USE master; GO --Set the database to READ_ONLY ALTER DATABASE ReadOnlyDB SET READ_ONLY; GO USE ReadOnlyDB; GO --Check the File & File-group properties SELECT sfg.is_read_only,sfg.* FROM sys.filegroups AS sfg; GO SELECT sdf.is_read_only,sdf.* FROM sys.database_files AS sdf; GO As can be seen from the output, none of the...(Read whole news on source site)