I recently completed a seven-post series on the IBM Watson Developer Blog about Cognitive System Testing. \u00a0These posts reflect some hard-learned lessons from the past few years. \u00a0Cognitive systems present some interesting challenges for testing-minded people, some of these challenges are unique to cognitive systems and some are common to all software systems.<\/p>\n
Part 1: How to test a cognitive system (and why it\u2019s so important)<\/a>, this includes guiding principles and sets up the series.<\/p>\n Part 2: Cognitive system testing: Smoke testing<\/a>, after all the most important question to answer quickly is “is my cognitive system on fire?”<\/p>\n Part 3: Cognitive system testing : Testing at the beginning with ingestion verification test<\/a>, since a cognitive system is only as good as the data you are loading into it.<\/p>\n Part 4: Cognitive system testing: Natural language processing unit testing<\/a>, because\u00a0testing NLP is both hard and important.<\/p>\n Part 5: Cognitive system testing: Overall system accuracy testing<\/a>, users judge the system by its accuracy and you should too.<\/p>\n