In the previous post we added unit tests for the AngularJS code running on the client. And while these tests are important there is more to test. After all the client side code depends on a server side WebAPI controller and a RavenDB database. In this post we are going to add unit tests for those two. To inject or not to inject dependencies Normally when one class depends on another it is best to use dependency injection to get one to use another. And the dependency is then based around interfaces so
a dependency can be faked during testing. The MoviesController is the WebAPI controller that publishes our movies. This results in it having a dependency on the RavenDB IDocumentStore. Now we could create a fake IDocumentStore implementation but the recommendation from Ayende Rahien with RavenDB is not to do so and user the real thing with an in memory database. And because we are already using the EmbeddableDocumentStore that loads its connection info from the application configuration file all we need to do is specify the appropriate connection string for our unit tests.
Today, along with the Office team, we are a releasing a number of significant updates for developers building apps that interact with the Office ecosystem. Whether you are building a mobile app that wants to connect to high-value data and services in Office 365, developing rich integration into Office experiences with a custom app for Office, or developing Cloud Business App projects that integrate with SharePoint, today's releases enable developers to connect to the Office ecosystem in new and exciting ways. Applications are increasingly being built by composing high-value data and services together to deliver unique mobile, desktop and web experiences.
Today's Office 365 API releases let developers consume Office data and service from any application, and today's Office Developer Tools for Visual Studio and "Napa" releases let developers build new kinds of application experiences within Office apps. Here's a few of the exciting features in today's releases – for full details check out: The Office 365 Platform blog The Visual Studio blog Office 365 REST APIs Preview Office 365 provides a wealth of high-value data and services for business applications. Today, Office is exposing these data and services via a new, simple and consistent set of Office 365 REST APIs. This release...(Read whole news on source site)
Today at SharePoint Conference 2014, we are thrilled to announce that Office Developer Tools for Visual Studio 2013 – March 2014 Update is available to download! The March 2014 Update ships with a ton of new features that improves support for Office 365 Cloud Business App and apps for Office/SharePoint in Visual Studio 2013 RTM. It also allows you to build new types of apps for Office that are enabled in Office 2013 SP1 and Office 365. In addition, “Napa” Office 365 Development Tools is also being updated, which means you can start building new types
of apps for Office anywhere through your web browser as long as you sign up for an Office 365 Developer Site. In this article, I’m excited to share with you more details about these new features. Office 365 Cloud Business App (CBA) Visual Studio 2013 introduced the new Cloud Business App project template which enables developers to quickly build modern business applications that can integrate with and extend the Office 365 platform experience. In this update, we’ve been focusing more on increasing the productivity or developers building this class of applications. Additional capabilities have been added...(Read whole news on source site)
Microsoft will be making some big changes as to how Office 365 looks and works later this year with the addition of new Office Graph and 'Oslo' technologies.
The next on-premises versions of Microsoft's Exchange Server and SharePoint Server won't be available until some time in calendar 2015.