SAMPLE OF THE DIAGNOSTIC MESSAGES

The overwhelming majority of the following diagnostic messages can be efficiently generated automatically. We marked explicitly a few exceptions where, at present, we must resort to (semi-)manual testing.

1. `System error, `, "ran out of memory"

2. Answer Wrongly Depends On The Integration Variable

3. Error, (in collect/series) too many levels of recursion

4. Error, (in collect) too many levels of recursion

5. Error, (in signum/main) too many levels of recursion

6. Error, (in evalf/int) cannot assume on a constant object

7. Error, (in expand/Psi) too many levels of recursion

8. Error, (in floor) floor is not differentiable at integers

9. Error, (in gcd/doit) too many levels of recursion

10. Error, (in int/cook/ngritty) wrong number (or type) of parameters in function
diff

11. Error, (in inttrans/normalize/exp/classsimp) unable to compute coeff

12. Error, (in int/definite/contour/polypow) numeric exception:

13. Error, (in int/denoms) too many levels of recursion

14. Error, (in int/ellalg/trxstandard) must be 3 or 1 real roots

15. Error, (in limit/mrv/limsimpl) too many levels of recursion

16. Error, (in limit/range) cannot determine if this expression is true or
false

17. Error, (in limit/range) invalid terms in sum

18. Error, (in limit/range) should not happen 33

19. Error, (in limit/range1) too many levels of recursion

20. Error, (in limit) inconsistent direction with infinities

21. Error, (in limit) invalid limiting point

22. Error, (in ln) numeric exception: division by zero

23. Error, (in property/OrProp/*) too many levels of recursion

24. Error, (in Psi) numeric exception: division by zero

25. Error, (in series/exp) division by zero series

26. Error, (in simpl/simpl/ReIm/sum) too many levels of recursion

27. Error, (in simpl/trunc) trunc is not differentiable at non-0

28. Error, (in type/radfun) too many levels of recursion

29. Error, (in unknown) too many levels of recursion

30. Error, (in Zeta) numeric exception: division by zero

31. Error, simpl/abs: missing system function

32. Execution stopped: Memory allocation failed. The kernel has been shut
down.

33. Human Unreadable Output

34. Invalid Im Magnitude

35. Invalid Im Sign

36. Invalid Indefinite Integration

37. Invalid Page Fault

38. Invalid Re Magnitude

39. Invalid Re Sign

40. Invalid Re/Im Magnitude

41. Invalid Sign

42. Meaningless Output

43. MSERVER caused an invalid page fault in module MAPLE.DLL at <base:offset>

44. Numeric Value Is Unavaliable

45. Regression Case

46. Semi-Finished Computation

47. Spurious 'undefined' Is Returned

48. Spurious Convergence

49. Spurious Divergence

50. Strange Limitation

51. Too Much Complex Answer - Can be Compressed <number> times

Right away, the following requires manual diagnostics, but I keep working on the point.

52. Incorrect Graph

53. Disappeared Graph

54. Disappeared Axes

It is extremely difficult to propose an efficient automatic methods for

55. Documentation: Mistype

56. Documentation: Missed Feature

57. Documentation: Incorrect Description

About the connectivity questions, I believe that really valuable things could
be finally done

to automate the testing here but I need a special research to
make the clear-cut statements.

© 2002-2008 Cyber Tester Ltd. All rights reserved. All logos and trademarks are property of their respective owners.

E-mail: vb@cybertester.com

© 2002-2008 Cyber Tester Ltd. All rights reserved. All logos and trademarks are property of their respective owners.

E-mail: vb@cybertester.com