Crud methodology in software testing...
I am writing a new blog for fresher or recently joined software industry, generally when people will join gaining industry and mobile application testing for any platform. Everybody is having a basic idea of testing game because now gaining is a very big industry. About application testing now a day everybody is having a Gmail account and other sites. So everybody is having an idea about what is software and where it will be used and why used and how it will make our life easier. This is a general idea why we are creating a product simple to make our life more easier. Same why we are creating software, only scope is different. Generally in a gaming or u can say in mobile industry companies are not involve in more documentation there r few reason or challenges everyday, ex daily new launch handsets, no of OS, diff memory size, screen size, and less time to complete the project and we have another problem, very difficult to check the overall performance battery consumption for each application, run time memory allocation, data transfer speed in 2g or in 3g.
Ok, we will talk about crud methodology, this methodology is used in any domain crud means create, read, update and delete.
When ever u start writing test case or SRS or Frustum can use crud methodology even creating smoke test u can use crud methodology.
Lets take an example:
The user interface level of most applications. For example, in address book software, the basic storage unit is an individual contact entry. As a bare minimum, the software must allow the user to
Create or add new entries
Read, retrieve, search, or view existing entries
Update or edit existing entries
delete existing entries
without at least these four operations, the software cannot be considered complete. Because these operations are so fundamental.
With the help of this method u can create a test case...in next blog I will tell u how to write a test case and what are the imp factors while writing test case...that all for the day
Ok, we will talk about crud methodology, this methodology is used in any domain crud means create, read, update and delete.
When ever u start writing test case or SRS or Frustum can use crud methodology even creating smoke test u can use crud methodology.
Lets take an example:
The user interface level of most applications. For example, in address book software, the basic storage unit is an individual contact entry. As a bare minimum, the software must allow the user to
Create or add new entries
Read, retrieve, search, or view existing entries
Update or edit existing entries
delete existing entries
without at least these four operations, the software cannot be considered complete. Because these operations are so fundamental.
With the help of this method u can create a test case...in next blog I will tell u how to write a test case and what are the imp factors while writing test case...that all for the day
Comments
Post a Comment