Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

Connection, not collection: Thats the essence of knowledge management.

Thomas A Stewart, Tom The Wealth of Knowledge

Thomas A. Stewart is Chief Marketing and Knowledge Officer for global management consulting firm Booz & Company. Stewart is a best-selling author, an authority on intellectual capital and knowledge management, and an influential thought leader on global management issues and ideas. - See more at: http://www.booz.com/global/home/who_we_are/leadership/50635169/tom_stewart#sthash.eoXBG6kM.dpuf
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 2

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

Atha yadi te karma-vichikitsA vA vrtta-vichikitsA vA syAt ye tatra BrAhmanAh sammarshinah yuktA AyuktAh alukshA dharmakAmAh syuh yathA te varteran tathA vartethAh Atha abhyAkshyAtesu ye tatra BrAhmanAh sammarshinah yuktA AyuktAh alukshA dharmakAmAh syuh, yathA te tesu varteran tathA tesu vartethAh Esha Adeshah esha upadeshah YeshA vedopanishatEtat anusAshanam evam upAsitavyam evam u ca etat upAsitavyam.

In brief, Upanishad says if you have a doubt, get it clarified, either refer to a live case study of a virtuous person, or meet the Virtuous person to get a solution. Knowledge gives humbleness, based on which one gets the character, based on character money flows (Income), then the charity (Giving) and finally the satisfaction Sukha

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

 Space Check. Water Availability. Electronic gadgets usage. Car Parking. House Security. Neighborhood. Availability of facilities. Owners approach/Rules. Shifting of Existing items. No of Pax. Rent.
Monday, October 28, 2013

DB Space. Infrastructure. Gadget/SW integration. Server Space. Antivirus. Lan. Features of a SW/Gadget. Scalability. Legacy Data Migration. Login Users. Login Cost
7

Designed and Compiled by Nataraj Viswanathan

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

 The Nature - Mother of all inventions. Keen observation of nature and understanding the nature has brought in the greatest inventions. In the next few slides, we are talking about testing, in context to nature. The idea is to learn from the nature which can help us in focusing on the testing platform. Testing should be treated as an art, as it differs the way or approach based on individual skills. However one needs to have the passion for this job, to excel. The nature , and the animal, bird behavior gives us more learning on testing.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 9

Black box testing Testing done based on Requirement not based on internal design. Normally POC users do this. White/Glass box testing Testing done based on knowledge of the internal logic of an application. Normally done at product Development side. Unit testing Software components or modules individually undergo this type of testing. Normally done by Developers or programmers. Functional testing Testing done based on perceived output or requirement. Can be also linked to Black-box type testing. Acceptance testing Can be referred as UAT. (Post Development) Beta testing Testing done by end-users before releasing application for Designed and Compiled by Nataraj Monday, October 28, 2013 10 commercial purpose. Similar to UAT. Viswanathan

Integration testing Testing done to verify combined functionality. This normally spreads across multiple applications or servers, gadgets so on. Incremental Integration testing is done along side when new modules or applications get added. System testing Test covers the entire system, some thing similar to black box. End-to-end testing Complete environment, is tested, normally done before delivery of a agreed project. Sanity testing This testing is done to identify if the application is ready for testing. Regression testing Testing done as a whole post any module development changes, normally automation tools are used by for these types of testing. Designed and Compiled Nataraj
Monday, October 28, 2013 Viswanathan 11

Recovery testing Testing how recovery happens post a crash or failure. Be it HWare or SWare. How fast and how accurate is it. Load testing Testing performance for applications under heavy loads. Simple few or many transaction using multiple login or few logins. Stress testing Testing when the System is stressed. Reason could be many , DB size or load, Increasing the logins, Same transaction attempted by many, Complex queries so on. The idea is to understand the point where it breaks. Security testing Testing the system how well it is protected, Be it internal Designed and virus Compiled by Nataraj password related or external attack. Monday, October 28, 2013 12
Viswanathan

Performance testing Similar to Stress & or load testing. Usability testing Testing the user friendliness, ease of usage, navigation etc. Compatibility testing Testing to understand performance during various scenarios hardware/software/operating system/network environment and or combinations. Comparison testing Testing in comparison to previous versions or other similar products. Alpha testing Testing done Post development prior to Delivery or Go-live. Gives room for Smaller or last moment changes.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 13

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

14

Perfectionist

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

15

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

16

 Who is a Tester? What is the difference between a Tester & User? Why Testing is required? Who should do testing? What kind of Testing is required? What is Functional and Technical testing? What is UAT? Is UAT required if so how many times? How much time is required for Various Kinds of testing? Who should write the test plan & Test cases? Are test cases important? What is the importance of having Test Data? What is the importance of Automating testing?
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 17

 Are Timelines important, if so how to plan? Planning the prerequisites for a testing, how important is it? Each configuration needs to be tested simultaneously or parallel? Testing almost comprises of 25% of the Project timelines, how to distribute timelines? Integration testing both with other gadgets and software applications?

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

18

Nature & Knowledge of its behavior teaches on how to behave under different life circumstances.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 19

 Consider the tree as an Application. The trunk, roots, branches are the architecture and or base Product functionality. Each new branch, or stem is the newer modification. Applications could differ based on base product or the ratio of customization done. Every tree is a home to many reptiles, birds and creatures, considered as users or Testers. Understanding the testing need, scope & End users are a must.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 20

 Consider the Serpent As a Tester or User too. It moves in a specific path based on where the prey is. It is confident of its movement and quite sure of the Prey. They do not get distracted by external factors, while searching a prey. Snakes are far sensitive, and can sense the prey even if at a distance. Snakes when they creep, follow a certain path or Process. Process Knowledge and flow becomes a prerequisite for a tester. Reminds us of White or Glass box testing.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 21

 Monkey is an animal, non static, does not follow Process, jumps hey ware. It not only uses the branches to hop , but also climbs, down to the root level. As they move, they some time copy each other Gestures. Sometimes they become totally silent, sitting idle for hours rubbing the branches. Move up the branches to have a broad view of appearing danger. Be prepared of futuristic changes, explore the application erratically to understand the behavior. Reminds us of regression, negative testing. Designed and Compiled by Nataraj Monday, October 28, 2013 22
Viswanathan

 Chameleon are silent reptiles, often appears nodding their head up and down. Chameleons change their skin color similar to the place they creep in. They stay silent for most of the times as if they are thinkers. They catch their prey sitting at a place, by extending just the tongue. Be vigil like chameleons, change your color (be in other mans shoe), think like a soft user, a thug, an auditor, & as an entrepreneur. Think also differently at every step.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 23

 Ants always move in groups , they always form a line, where required, or appear as a heap. Ants almost carry more than its body weight. Exhibit a very good division of labor attitude. Quickly reform their lines even if disturbed by external factors. Team work is very essential while in testing. Helps in multiple application , multi user scenario, non stop transactions, creating roles for each testers are learning's from this.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 24

 Woodpeckers are real messy birds. They keep flying while pecking the wood. They almost create a dent on the wood, by creating a hole. They normally appear single and not in a group. Some users create such dent, creating a irreparable change to the application either an architecture change or a change in process. One has to be aware of such changes as it may change the testing scenarios too.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 25

 Worms work invisibly, deep inside the mud. They work blind folded. Touch them, they shrink, and become silent for sometime. Available like a heap some time, are known to create fertility by their work process. Many application users do work silently. Much required manpower, for testing of larger setups. Users if not exposed much, change management becomes a challenge. Training and knowledge share of New gadgets, and or process becomes essential.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 26

 Lightning, rain, storm do have an impact on trees. Impact is either good or bad, sometimes neutral too. Applications too face impacts from external factors. Could be change in OS, New updates in existing OS, Connectivity changes. Users aware of such factors are well informed and quite prepared to tackle the same. Sometimes change In technology, could make an application obsolete.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 27

 Most of the trees bear fruits. When ripened they fall. Farmers and or Gardeners normally have a count when the fruits grow and are also tallied if plucked or collected. Applications too post transactions Data behaves like a fruit. These data could be fetched or auto flowed to another destination. Control totals either from actual Qty or weight becomes important .
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 28

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

29

 Reports as a requirement has many testing scenarios could be thought and furnished prior to development, which reduces the testing time. Printer to be used Headers to be repeated in each page. Usage and business benefit. Font size, coloring logic, Bold fonts usage, Underlining, so on. Report download formats apart from preview. Keeping filters common for all reports, and activating required filter as per need of report. Data security. Well Documented FS, TS reduces the re-alteration & saves time.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 30

 Attach greater significance to testing, for it can create or destroy the whole. Plan strategically the timelines for Creation of test plans Creation of Test cases Validation of test cases & Types. Actual testing based on type. Never attach humane to this job, nor imbibe or create perceptions, for it is just a process. (Hammer like a Gold or Black smith) Sharing the test output legibly and with understanding helps faster fixes or resolutions.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 31

 A good process documentation either writing or reading, does instigate and creates ideas of what and how to test. It is important to stamp time & Date both for creation and or testing of test case data. Tag each line of test case with the tester. Keeping in pace to the project timelines is a challenge as there are many who join the testing Gang & does not have a clue on Project timelines. Understand the behavior of a developer, Tester, it helps to understand the application as well as the impending issues which are likely to come. For E.g., cut & paste, repeated bugs of same nature, e.tc. Programming Logic.
Monday, October 28, 2013 Designed and Compiled by Nataraj Viswanathan 32

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

33

Try these for more

http://www.softwaretestingclub.com/ http://www.ece.cmu.edu/~koopman/des_s99/sw_testing/

For Queries Write to nataraj@titan.co.in natwarlal1968@gmail.com

Designed and Compiled by Nataraj Viswanathan

Monday, October 28, 2013

34

Download link: (incase ppt does not reach you by email) http://www.slideshare.net/NatarajV1968/application-testing-an-art

Monday, October 28, 2013

Designed and Compiled by Nataraj Viswanathan

35