As we move to the final component of the database server, tests should aim to uncover indexing issues and table lock issues with data sets that mimic the production environment. If the application under test is new, it should be tested with a projected data set of at least one year. Database failover tests should also be included to check for any application downtime when the database servers get into a hot-cold mode. During this time, if the application is still in use, tests need to verify different errors that the user would encounter.
In summary, in the current application-testing scenario, a tester’s role is not limited only to functional, automation, or performance testing. He also needs to understand the application’s architecture and challenge the design without worrying about stepping into an architect’s shoes. Executing detailed architectural testing helps document the application’s behavior, which can then be published to eliminate any surprises or anxieties and to minimize the application’s components’ glitches and hiccups.
| Attachment | Size |
|---|---|
 Chauhan_Wearing_02.pdf | 189.43 KB |
Pages
About the author
As chief technology officer of QA InfoTech, Kunal Chauhan is focused on driving technology and strategy as the company moves into additional vertical markets and technology areas. Prior to joining QA InfoTech, Kunal was VP of web applications development in Thomson Reuters' equities division for twelve years where he was responsible for building and managing more than twenty applications including real-time, historical, TCA, and query-based systems serving brokerage houses and financial institutions. Kunal has also worked for two years in Fidelity Investments' corporate actions group.
