Advertisement
Guest User

Untitled

a guest
Jun 29th, 2016
71
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.25 KB | None | 0 0
  1. changes to be made
  2. ==================
  3.  
  4. - arguments.py - change the config actions, it basically checks for arguments to make sure everything is ry
  5. - Automarshalling - makes sure diff formats, is checked for errors
  6. - cafe manager.py - Testenvmanager - sets all the env manager, it makes sure all the env sets
  7. - the cafemaster.log has the log file name that is used to name to log files
  8. - ccniel - do we need a env variables at all?!
  9. - nathan - we need the env variables, as in jenkins we dont have access tthe file system, we need to set variables in jenkins , thus going for env variables is always easy.
  10. - create a mock tool to just print the env variables, and first use cafe components and then use our own design, so that we can swap
  11.  
  12.  
  13. - opencafe/drivers/uniitest/fixtures.py
  14. - logdescripiton - for test name
  15. - reporter - is to store all the pass/fail details as a csv - may be give an api access to it, so that this data can be pushed to ES/kibana
  16. - nathan - would probably include
  17. - nathan - this is where individual files are created (in the setup class)
  18. - nathan - for syntribos every test is a class, so if we blow the fixutre, then all logs would be in a single file, not optimal.
  19.  
  20. - runner - has a set test env - Testenvmanager - so remove it
  21. - nathan - its a bad design choice, engine config should read env vairbales, and all env variablses shuld be set at the begining and every class should read the engine config file.
  22.  
  23. - multithreading - opencafe - parallel runner in unit test is a way to approach to choose if we need to do a parallel syntribos - the master log is the issue if things are not handled properly then the master log would be overwritten.
  24. - textfixture - we need to write our own fixtures, we dont need the cafe fixture
  25.  
  26.  
  27. how should we do it?
  28. ====================
  29.  
  30. - make a master config file - Base config
  31. - endpoint and identity info
  32. - All relevant paths
  33. - request templates
  34. - payloads
  35. - base config
  36. - log files
  37. - Test config
  38. - time diff
  39. - body diff
  40. - turn of tests - eg ddos
  41. - section headings for diff test types
  42.  
  43.  
  44. - default location for configs is ~/.config/syntribos/
  45. - All user defined templates - we can change the config for user defined tempaltes in the config
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement