{"id":37928,"date":"2016-10-21T04:39:12","date_gmt":"2016-10-21T09:39:12","guid":{"rendered":"http:\/\/ingsagnelliblog.wordpress.com\/?p=374"},"modified":"2016-10-21T04:39:12","modified_gmt":"2016-10-21T09:39:12","slug":"test-me","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/test-me\/","title":{"rendered":"Test me!"},"content":{"rendered":"

“Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not.” (TutorialsPoint, 2016)<\/p><\/blockquote>\n

Software needs to be tested to determine if all requirements were met. If there are any errors, bugs, mistakes, or gaps in the system.<\/p>\n

Who does testing?<\/h2>\n

The more the better. Different points of view are required in this process: Normally, there is a software testing team; however, software developers, managers, and users also participate.<\/p>\n

It is important to implement this phase throughout the development.<\/h2>\n

Why? To save time, reduce costs and errors.<\/p>\n

Testing never ends<\/h2>\n

This means that there is always some improvement to the system; therefore, testing is needed to see if there is something to be improved.<\/p>\n

Types of testing:<\/h2>\n

There are lots of testing types including compatibility, performance, usability, security, recovery, comparison, stress, unit, load, regression, system, etc.<\/p>\n

Most known testing types are alpha testing which is done at the end of the development phase, where the software is almost complete; beta, where end-users are the ones testing the system supposedly finished; and black-box which tests if the system covers requirements.<\/p>\n

Video:<\/h2>\n