Test Case Naming 02

6,171 views

Published on

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
6,171
On SlideShare
0
From Embeds
0
Number of Embeds
21
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Test Case Naming 02

  1. 1. TEST CASE <br />NAMING CONVENTION<br />Srilu Balla<br />Lake Oswego OR<br />October 20 2010<br />
  2. 2. What does a test case belong to?<br />
  3. 3. The test cases come from requirements<br />So, it may seem like the test case name should be mapped to the requirements or use cases.<br />But what happens if the requirements change?<br />
  4. 4. The requirements change, new requirements come up, some requirements do not see the light of the day.<br />Is it practical to change the test case with the changing requirement? <br />Even with versioning will it make sense on the long run?<br />
  5. 5. NO<br />
  6. 6. New test cases arise from new projects intended to improve or modify a system<br />
  7. 7. So, it might seem like the test case name should reflect the project which initiated it.<br />But the projects end at some point. New teams and team mates take over the system maintenance, testing and other improvements.<br />Is it useful to learn about the project ?<br />Is there any value to learning about an ancient project?<br />
  8. 8. NO<br />
  9. 9. What does a test case belong to?<br />
  10. 10. A Test case always belongs to the product<br />
  11. 11. That is correct.<br />Projects come and go<br />Requirements come , change and go<br />But the core product is forever<br />(I mean as long as it lasts)<br />
  12. 12. The test case must aid in identifying the product it belongs to .<br />A company may have only one product currently, but there is every chance the company could introduce new products. Always be prepared for change.<br />The first part of the test case should always reflect about the product it belongs to<br />
  13. 13. What is a test case named after?<br />Example test case name<br />Let us try naming for Microsoft Power Point application.<br />Since Microsoft has several applications under Microsoft Office, we will have to indicate which MS Office application the test case belongs to<br />MS_PPT_TestCaseor PPT_TestCase might be ideal.<br />
  14. 14. Example test case name 02<br />Let us try naming for Google applications.<br />Since Google has several applications, the naming should help identify the concerned product<br />“G_GM_TestCase” or “GM_TestCase” for Google Mail<br />“G_GC_TestCase” or “GC_TestCase” for Google Calendar<br />“G_GD_TestCase” or “GD_TestCase” for Google Documents<br />“G_GMap_TestCase” or “GMap_TestCase” for Google Maps<br />“G_YT_TestCase” or “YT_TestCase” for You Tube<br />
  15. 15. Example test case name<br />Let us try naming for Microsoft Power Point application’s First elements (parts)<br />Since the Menus are the first elements in a PPT, let us try naming a test case relating the first elements.<br />“MS_PPT_mHome_TestCase or “PPT_Home_TestCase”<br />MS = Microsoft<br />PPT = Power Point<br />mHome= menu Home, <br />Home = first element Home.<br />Test Cases for other elements in the test<br />
  16. 16. Example test case name<br />Let us try naming for Microsoft Power Point application’s Second elements (parts)<br />The second elements in a PPT’s Home menu are the groups. The group “clipboard” consists of elements - Paste, Cut, Copy, Former Painter etc.<br />“MS_PPT_mHome_gClipboard or “PPT_Home_Clipboard”<br />mHome= menu Home<br />Home = first element Home<br />gClipboard= group Clipboard<br />Clipboard = second element Clipboard<br />Test Cases for other elements in the test<br />
  17. 17. Naming for Microsoft Power Point application’s Third elements (parts)<br />The third elements in a PPT’s Home menu’s Clipboard group are the - Paste, Cut, Copy, Former Painter etc. Test case for these elements would be names like – <br />“MS_PPT_mHome_gCl_iCut or “PPT_Home_Clip_Cut”<br />mHome= menu Home<br />gClipboard= group Clipboard<br />Clip = second element Clipboard<br />iCut= icon Cut<br />Cut = third element Cut<br />Test Cases for other elements in the test<br />
  18. 18. Naming for Microsoft Power Point application’s Fourth elements (parts)<br />The fourth elements in a PPT’s Home menu’s Clipboard group’s Paste icon are - Paste, Paste Special, Paste as Hyperlink, Duplicate. Test cases names for these elements could be –<br />“MS_PPT_mHome_gCl_iP_oPasteSpecial” or “PPT_Home_Cl_P_PasteSpecial” <br />iP= icon Paste<br />P = third element Paste<br />oPasteSpecial= option Paste Special<br />PasteSpecial= fourth element Paste Special<br />Test Cases for other elements in the test<br />
  19. 19. List of suitable test case names for MS-PPT<br />MS_PPT_Invoke<br />MS_PPT_mHome_iCut<br />MS_PPT_mHome_iCopy<br />MS_PPT_mHome_iFormat Painter<br />MS_PPT_mHome_iPaste<br />MS_PPT_mHome_iPaste_oPaste<br />MS_PPT_mHome_iPaste_oPaste Special<br />MS_PPT_mHome_iPaste_oPaste as a Hyperlink<br />MS_PPT_mHome_iPaste_oPaste Duplicate<br />Sample test case names<br />
  20. 20. Do test cases need hierarchy?<br />The test case could also be named as MS_PPT_Cut, a seasoned tester or a new tester would understand what the test case deals with.<br />But if Microsoft one day decided the Cut did not belong in the menu Home but in the menu Review, how will any tester guess where the cut icon is located?<br />Hierarchy helps in identifying the navigation and location of the element needed for testing. <br />Hierarchy for Test cases!?!?<br />
  21. 21. Functionality for / in Test cases<br />Test cases can have an intended functionality in the name<br />MS_PPT_mHome_iCut_Remove<br />MS_PPT_mHome_iCut_Add<br />MS_PPT_mHome_iCut_Modify<br />MS_PPT_mHome_iCut_Edit<br />MS_PPT_mHome_iCut_Delete<br />MS_PPT_mHome_iCut_Insert<br />MS_PPT_mHome_iCut_nameChangedto_Bite<br />(by eye balling the test case name the intended test can be assumed or understood along with navigation & hierarchy)<br />
  22. 22. Identify the Elements for TESTING<br />Example with PPT menus<br />
  23. 23. View of Test case Hierarchy<br />Level 0 Test cases usually deal with one time test functions. <br /> These tests may need to be executed only one time.<br />These tests are crucial and they may not be as straight forward as testing the UI.<br />(I prefer to have them in Level 0, unless Level 0 tests are validated, I won’t touch the rest of the tests. Once bitten twice shy)<br />(Cont..)<br />
  24. 24. View of Test case Hierarchy<br />Unless the Level 01 tests pass, the Level 02 tests may not be executed. Because they will obviously fail. <br />Dividing into Levels saves time (You already know how valuable time is)<br />
  25. 25. More Functionality<br />The function CUT can be performed by another means too. With CTRL + X<br />So where does the test case to test this functionality go? And how should it be named? And where does it stand in the hierarchy?<br />The short cut keys are not specific to PPT . They work in almost every Windows application.<br />Still it is necessary to include them in the tests.<br />So how is this done?<br />
  26. 26. The function CUT can be performed by another means too – CTRL + X<br />MS_sk_Ctrl+Xor MS_sk_CUT<br />sk= Short cut Key<br />Ctrl + X = key Control + keyX<br />CUT = function to CUT<br />The test case is not tied to an application. But it may be tied to Microsoft (so, “MS_” is appropriate). By indicating that it is a test case for short cut key, the tester can assume where it might be applicable.<br />More Functionality<br />
  27. 27. Summary<br />Test Cases belong to the product. <br />Test Cases aim to test the specifications as per a requirement<br />Test Cases are a result of a project initiated.<br />But test cases belong to the product.<br />Average life of software is 7 years.<br />A test case we create today is the guide for users, testers, developers, project managers etc. to understand the functionality and purpose of a system. <br />The need to study the high level requirements, business cases, use cases etc can be eliminated with one well written test case.<br />This is a necessary art that is taken for granted.<br />
  28. 28. Thank you for taking the time to read my views and strategy for test case naming convention. <br />I have not yet come up with suitable name for this strategy.<br />I am always open to suggestions as well as questions. Please feel free to leave your comments and any unusual situation you might be facing with test case naming convention – together we can come up with a solution.<br />(The views in this document are solely mine. If any of you out there developed a similar strategy – Kudos to you. I would like to know you.<br />Please know that my strategies are a product of my efforts to streamline QA maintenance procedures<br />More documents to follow ………)<br />Thank You<br />

×