Testing

Data Migration Testing Data migration is a process which involves the migration of data from an existing legacy system to a new system. Whenever an organization decides to upgrade or change its database, it will need to transport the existing data to the new database. Data migration activity includes everything that is required with respect to data to ensure that the new database is up and running without any defects and it also contains all the legacy data ( data that is present in the existing database) , and the data has been migrated to correct table(s) and column(s). During this data migration there may be possibility of data missing or data corruption. So after the data migration process one has to test whether the whole data is migrated successfully or not, whether something is missing or got corrupted during migration. So data migration testing is to compare migrated data with original data to find out any discrepancies. Two types of data Load:

A data warehouse: is a relational database that is designed for query and analysis rather than for transaction processing. usually contains historical data derived from the transaction data, also data from other sources. It separates analysis workload from transaction workload and enables an organization to consolidate data from several sources. 3. is subject-oriented, integrated, time-variant and non-volatile collection of data in support of management's decision making process. Subject-Oriented : A data warehouse can be used to analyze a particular subject area. Integrated: A data warehouse integrates data from multiple data sources. Non volatile: Data once loaded is usually never changed.   Time-Variant: Historical data is kept in a data warehous A data warehouse environment includes: an extraction, transformation, and loading (ETL), an online analytical processing (OLAP) engine, client analysis tools, and ot

A surrogate key may also be called as: synthetic key entity identifier system-generated key database sequence number fact less key technical key arbitrary unique identifier -It is the system generated key which cannot be edited by the user. -It is the primary key of the dimension table in warehouse. -It is nothing but the sequence which generates the numbers for primary key column . Surrogate keys are system generated keys. They are integers. Surrogate keys are extremely useful when having type 2 data (i.e. storing historical information) For ex: Consider one has a table in which a person and his location are stored. Now when his location is changed and we want to keep a historical record of the same it is stored with a surrogate key that will help us to uniquely identify the record. This is also a reason that OLTP keys are not used in the warehouse and a separate dimension or surrogate key is maintained . What is the data type of the surr

Purpose: Defect Density is used to detect the rate at which developers are generating defects Definition Defect Density is the number of confirmed defects detected in software/module during a defined period of development divided by the size of the software/module. Formula Defect Density = Defect/unit size Unit size=Size is typically counted either in Lines of Code or Function Points.

Address validation on e-commerce application Let’s discuss on how we write test cases for address validation in an e-commerce application: If fields are editable If fields take maximum and minimum characters length If all the button are functional If address entered is standardized meaning correct and valid address has been entered If address entered in front end is getting loaded @ table level Can able to modify the address? Can able to delete the address? Phone number field validation (validation for # of digits and if it is allowing special characters or not) These are the few test cases which came to my mind and these may get change depending on the functionality of the application