← Back to context Comment by u_sama 1 day ago That is what the testing suite is there to check, no? 5 comments u_sama Reply layer8 1 day ago No. Testing generally can only falsify, not verify. It’s complementary to code review, not a substitute for it. kneel25 1 day ago You mean the testing suite generated by AI? trflynn89 1 day ago The primary JS test suite is maintained by the authors of the specification itself: https://github.com/tc39/test262 Jolter 1 day ago It isn’t, in this case. u_sama 1 day ago No, a real test suite, either their own which they developped or the official ECMA one
layer8 1 day ago No. Testing generally can only falsify, not verify. It’s complementary to code review, not a substitute for it.
kneel25 1 day ago You mean the testing suite generated by AI? trflynn89 1 day ago The primary JS test suite is maintained by the authors of the specification itself: https://github.com/tc39/test262 Jolter 1 day ago It isn’t, in this case. u_sama 1 day ago No, a real test suite, either their own which they developped or the official ECMA one
trflynn89 1 day ago The primary JS test suite is maintained by the authors of the specification itself: https://github.com/tc39/test262
u_sama 1 day ago No, a real test suite, either their own which they developped or the official ECMA one
No. Testing generally can only falsify, not verify. It’s complementary to code review, not a substitute for it.
You mean the testing suite generated by AI?
The primary JS test suite is maintained by the authors of the specification itself: https://github.com/tc39/test262
It isn’t, in this case.
No, a real test suite, either their own which they developped or the official ECMA one