SQA Software Quality Assurance 2019 SQA Lecture Grey

SQA Software Quality Assurance 2019

SQA Lecture: Grey Box Testing & General SQA Questions www. company. com

SQA Agenda q q q q Black box testing vs. White box testing vs. Grey box testing – Database testing Types of database testing Schema testing Database’s objects testing Myths or misconceptions related to Database testing General SQA Questions & Answers www. company. com

SQA Grey Box Testing – Database testing Case study & its objectives Let us consider a Banking application whereby a user makes transactions. Now from database testing viewpoint following things are important: § The application stores the transaction information in the application database and displays them correctly to the user. § No information is lost in the process. § No partially performed or aborted operation information is saved by the application. § No unauthorized individual is allowed to access the users information. § To ensure all these above objectives, we need to use data validation or data testing. www. company. com

SQA Fundamental differences between userinterface and data testing www. company. com

www. company. com

SQA Types of database testing The 3 types of Database Testing are: § Structural Testing § Functional Testing § Non-functional Testing www. company. com

SQA Structural database testing The structural data testing involves the validation of all those elements inside the data repository that are used primarily for storage of data and which are not allowed to be directly manipulated by the end users. The successful completion of this phase by the testers involves mastery in SQL queries. Schema testing The chief aspect of schema testing is to ensure that the schema mapping between the front end and back end are similar. Thus, we may also refer to schema testing as mapping testing www. company. com

SQA Structural database testing – Schema Testing Database table, column testing § Whether the mapping of the database fields and columns in the back end is compatible with those mappings in the front end. § Validation of the length and naming convention of the database fields and columns as specified by the requirements. § Validation of the presence of any unused/unmapped database tables/columns. § Validation of the compatibility of the § § www. company. com data type field lengths

SQA Structural database testing – Schema Testing § Keys and indexes testing § Important checks for keys and indexes § Check whether the required § § § Primary key Foreign Key Check whether the references foreign keys are valid. Check whether the data type of the primary key and the corresponding foreign keys are same in the two tables. Check whether the required naming conventions have been followed for all the keys and indexes. Check the size and length of the required fields and indexes. www. company. com

SQA Structural database testing – Schema Testing § § § Stored procedures testing Trigger testing Database server validations www. company. com

SQA Functional database testing The Functional database testing as specified by the requirement specification needs to ensure most of those transactions and operations as performed by the end users are consistent with the requirement specifications. Following are the basic conditions which need to be observed for database validations: § Whether the field is mandatory while allowing NULL values on that field. § Whether the length of each field is of sufficient size? § Whether all similar fields have same names across tables? § Whethere any computed fields present in the Database? www. company. com

SQA Functional database testing § § Checking data integrity and consistency Login and user security www. company. com

SQA Non-functional testing Nonfunctional testing in the context of database testing can be categorized into various categories as required by the business requirements. These can be load testing, stress testing, security testing, usability testing, and compatibility testing and so on. The load testing as well as stress testing which can be grouped under the gamut of performance testing serves two specific purposes when it comes to the role of nonfunctional testing. www. company. com

SQA Myths or Misconceptions related to Database Testing § Database Testing requires plenty of expertise and it is a very tedious job § § Reality: Effective and efficient Database testing provides longterm functional stability to the overall application thus it is necessary to put in hard work behind it. Database testing adds extra work bottleneck www. company. com § Reality: On the contrary, database testing adds more value to the overall work by finding out hidden issues and thus pro-actively helping to improve the overall application.

SQA Myths or Misconceptions related to Database Testing § § Database testing slows down the overall development process § Reality: Significant amount of database testing helps in the overall improvement of quality for the database application. Database testing could be excessively costly www. company. com § Reality: Any expenditure on database testing is a long-term investment which leads to long-term stability and robustness of the application. Thus expenditure on database testing is necessary.

SQA General Questions & Answers § § § Why do you want to be QAE? Why do you want to join this company? Are you enthusiastic & keen to learn? – self learner? Are you good in reviews? Example: resume Do you have a quality testing attitude? Are you a good observer? Difference btw Quality vs. testing? Difference btw Verification vs. validations? Attention to details? Bug life cycle? How to deal with dev to report a new bug? What are the common problems with software automation www. company. com