From 2958c0fe6233abaa1927ccc7149f3d78d2d98abe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Mon, 2 Feb 2015 11:22:45 -0800 Subject: [PATCH] Merge pull request #3007 from JoelOtter/patch-2 Add note linking to up-to-date doc on Flux website --- docs/_posts/2014-09-24-testing-flux-applications.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/_posts/2014-09-24-testing-flux-applications.md b/docs/_posts/2014-09-24-testing-flux-applications.md index f2728db83e..df83062035 100644 --- a/docs/_posts/2014-09-24-testing-flux-applications.md +++ b/docs/_posts/2014-09-24-testing-flux-applications.md @@ -3,6 +3,8 @@ title: "Testing Flux Applications" author: Bill Fisher --- +**A more up-to-date version of this post is available as part of the [Flux documentation](http://facebook.github.io/flux/docs/testing-flux-applications.html).** + [Flux](http://facebook.github.io/flux/) is the application architecture that Facebook uses to build web applications with [React](http://facebook.github.io/react/). It's based on a unidirectional data flow. In previous blog posts and documentation articles, we've shown the [basic structure and data flow](http://facebook.github.io/flux/docs/overview.html), more closely examined the [dispatcher and action creators](http://facebook.github.io/react/blog/2014/07/30/flux-actions-and-the-dispatcher.html), and shown how to put it all together with a [tutorial](http://facebook.github.io/flux/docs/todo-list.html). Now let's look at how to do formal unit testing of Flux applications with [Jest](http://facebook.github.io/jest/), Facebook's auto-mocking testing framework.