这里有一个事件网络示例,我一直在使用它来研究特定的一元操作的行为。我想要一种有原则的方法,而不是这种特殊的方法来测试我的代码。我知道如何测试我的功能,但考虑到reactive-banana 1.0.0
中的新设计选择,我正在寻找测试行为和事件的最佳实践
我遗漏了很多,希望我只包括了说明我的问题所必需的内容。请让我知道是否有遗漏,应该包括在内,以使问题更清楚。
makeNetworkDescription :: Parameters -> MomentIO ()
makeNetworkDescription params = mdo
eInput <- fromAddHandler (input params)
eTick <- fromAddHandler (tick params)
let
eValidated :: Event VAC
eValidated = toVAC <$> eInput
eClearBuffer = Clear <$ eBuffer
eBuffer ::Event BufferMap
eBuffer = bBuffer <@ eTick
bBuffer <- accumB (BufferMap (M.empty :: M.Map AID VAC)) $
manageBuffer <$> unionWith (clearBuffer) eValidated eClearBuffer
reactimate $ writeOut_Debug <$> eBuffer
缓冲区应该做的是累积玩家命令(然后在其他地方进行处理),然后在处理特定批次的玩家命令后清空。在下一次滴答声中,它又一次发生了。
我希望确保缓冲区在应该的时候被清除,并像应该的那样累积命令。现在,代码可以工作,我想写测试来确保它在我构建这个游戏时继续工作。
在上面的例子中,我可以使缓冲区Behavior
与Event
网络分离,但那怎么办?从测试中获得准确结果的最佳方法是什么?
编辑:更新-我相信这个链接将提供足够的提示。我会尝试一下,明天再详细报道。
编辑:更新-我写了一个单元测试。当它是purty时,我会上传到github,然后发布。上面的链接对整理该做什么很有帮助
编辑:更新-事实证明,如果你运行堆栈测试时出现类型错误,然后再次运行它,你会得到表明你的测试已经通过的输出。结果是,我并没有比昨天更接近。我有代码和一个更清晰的问题。我可能会为此开始一个不同的帖子
编辑:更新-我有一个测试在某种程度上是有用的,但我不知道该怎么办。我已经发布了整个项目的上下文。下面我只包括测试代码、错误和一些讨论。
main :: IO ()
main = defaultMain
[ testGroup "EventNetwork Input"
[testBuffer "bBuffer" Populated]
]
testBuffer :: String -> BufferState -> Test
testBuffer name Populated =
testCase name $ assert $ bufferPopulated (UAC (PlayerCommand (Move (ToPlanetName Mongo)) (AID (Data.Text.pack "100"))))
testBuffer name Empty =
testCase name $ assert $ bufferEmptied (UAC (PlayerCommand (Move (ToPlanetName Mongo)) (AID (Data.Text.pack "100"))))
bufferPopulated :: UAC -> MomentIO Bool
bufferPopulated ev = do
let eInput = ev <$ never
eValidated = toVAC <$> eInput
bBufferMap <- (buffer eValidated eClear) :: MomentIO (Behavior BufferMap)
let r2 = [(Just $ BufferMap $ M.insert (AID (Data.Text.pack "100")) (toVAC ev) (M.empty :: M.Map AID VAC))]
r1 <- liftIO $ ((interpret (eBuffer bBufferMap) []) :: IO [Maybe BufferMap])
return $ r1 == r2
bufferEmptied :: UAC -> MomentIO Bool
bufferEmptied ev = undefined
eBuffer :: Behavior BufferMap -> Event a -> Event BufferMap
eBuffer bBufferMap nvr =
bBufferMap <@ (() <$ nvr)
eClear = Clear <$ (() <$ never)
tests/Spec.hs:26:19:
No instance for (Test.HUnit.Base.Assertable (MomentIO Bool))
arising from a use of ‘assert’
In the expression: assert
In the second argument of ‘($)’, namely
‘assert
$ bufferPopulated
(UAC
(PlayerCommand (Move (ToPlanetName Mongo)) (AID (pack "100"))))’
In the expression:
testCase name
$ assert
$ bufferPopulated
(UAC
(PlayerCommand (Move (ToPlanetName Mongo)) (AID (pack "100"))))
问题归结为accumB
在MomemtIO
中创建Behavior
。如果我让bufferPopulated
返回IO Bool
,我该如何协调?
编辑:显而易见的是编写它想要的实例。我想这可能是转移注意力。你觉得怎么样。这和编写MomentIO Bool
实例一样简单吗?
编辑:更新我认为我走在了正确的轨道上。我已经注释掉了所有测试线束代码,并更改了bufferPopulated
的签名
bufferPopulated :: UAC -> IO Bool
bufferPopulated ev = do
let eInput = ev <$ never
eValidated = toVAC <$> eInput
bBufferMap <- liftMoment ((buffer eValidated eClear) :: Moment (Behavior BufferMap))
let r2 = [(Just $ BufferMap $ M.insert (AID (Data.Text.pack "100")) (toVAC ev) (M.empty :: M.Map AID VAC))]
r1 <- (interpret (eBuffer bBufferMap) []) :: IO [Maybe BufferMap])
return $ r1 == r2
我相信这应该有效,但这是错误
tests/Spec.hs:35:17:
No instance for (MonadMoment IO) arising from a use of ‘liftMoment’
In a stmt of a 'do' block:
bBufferMap <- liftMoment
((buffer eValidated eClear) :: Moment (Behavior BufferMap))
让我们从Reactive.Banana.Combinators
看一下MonadMoment
class Monad m => MonadMoment m where
An instance of the MonadMoment class denotes a computation that happens at one particular moment in time.
Unlike the Moment monad, it need not be pure anymore.
Methods
liftMoment :: Moment a -> m a
Instances
MonadMoment MomentIO
MonadMoment Moment
m
可以是任意的Monad
,IO
是Monad
。所以liftMoment
应该把Moment Behavior (BufferMap)
提升到IO Behavior (BufferMap)
,为什么不呢?我的推理有什么错?
答案来源于上一个答案。
活性香蕉的测试
interpretFramwork
需要一个新的签名。
interpretFrameWorks'' :: (Event a -> MomentIO (Behavior b)) -> [a] -> IO (b,[[b]])
interpretFrameWorks'' f xs = do
output <- newIORef []
init <- newIORef undefined
(addHandler, runHandlers) <- newAddHandler
network <- compile $ do
e <- fromAddHandler addHandler
f' <- f e
o <- changes $ f'
i <- valueB $ f'
liftIO $ writeIORef init i
reactimate' $ (fmap . fmap) (b -> modifyIORef output (++[b])) o
actuate network
bs <- forM xs $ x -> do
runHandlers x
bs <- readIORef output
writeIORef output []
return bs
i <- readIORef init
return (i, bs)