yesod-auth-oauth2/test/Yesod/Auth/OAuth2Spec.hs
patrick brisbin 9b028535bd
Add potential, currently non-functioning tests
Approach so far:

The SpecHelper sets up an example App type which should (theoretically)
be enough to get some fake requests and responses going, as in any
yesod-test-based suite.

The spec then tries to build an example plugin and make assertions on
how it dispatches. This is currently falling down on subsite-related
type errors (see commented attempts).

Another potential direction is to define the YesodAuth instance for App
to specify authPlugins built using the library. With that, we might be
able to create specs using yesod-test that exercise aspects of the
plugins in an indirect way, but enough to make useful assertions.
2016-01-04 13:02:09 -05:00

41 lines
1.2 KiB
Haskell

module Yesod.Auth.OAuth2Spec
( main
, spec
) where
import SpecHelper
main :: IO ()
main = hspec spec
spec :: Spec
spec = describe "authOAuth2" $
it "works" $ do
-- If I could somehow get this dispatch to execute, I could assert on the
-- response; at least enough to verify the state parameter that prompted
-- this track of work...
--
-- Currently, the blocker is that apDispatch is:
--
-- > HandlerT Auth (HandlerT App IO) TypedContent
--
-- but I really need a:
--
-- > HandlerT App IO TypedContent
--
-- to be able to use runFakeHandler, as is sort of shown below:
--
-- > let app = App
-- > plugin = authOAuth2 "example" undefined undefined
-- >
-- > x <- runFakeHandler
-- > M.empty undefined (getAuth app) $
-- > apDispatch plugin "GET" ["callback"]
-- >
-- > liftIO $ print (x :: TypedContent)
--
-- I basically need to peel one layer off the transformer stack, but I can't
-- find the right run-handler anywhere.
True `shouldBe` True