Yea, though I have to admit I didn't much time into figuring out what all
those == constants should have been to make it pass.


On Sun, Jan 27, 2013 at 4:43 PM, John Benediktsson <notifications@github.com
> wrote:

> In talib/tests/func_test.py:
>
> > +    def test_MAX(self):
> > +        result = func.MAX(series, timeperiod=4)
> > +        i = np.where(~np.isnan(result))[0][0]
> > +        assert len(series) == len(result), (len(series), len(result))
> > +        #self.assertTrue(result[i + 2] == 95.095)
> > +        #self.assertTrue(result[i + 3] == 95.095)
> > +        #self.assertTrue(result[i + 4] == 94.625)
> > +        #self.assertTrue(result[i + 5] == 94.625)
> > +
> > +    def test_BBANDS(self):
> > +        upper, middle, lower = func.BBANDS(series, timeperiod=20,
> > +                                            nbdevup=2.0, nbdevdn=2.0,
> > +                                            matype=talib.MA_Type.EMA)
> > +        i = np.where(~np.isnan(upper))[0][0]
> > +        self.assertTrue(len(upper) == len(middle) == len(lower) == len(series))
> > +        #self.assertTrue(abs(upper[i + 0] - 98.0734) < 1e-3)
>
> Broken test?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/mrjbq7/ta-lib/pull/18/files#r2787558>.
>
>