Please enable JavaScript.

Coggle requires JavaScript to display documents.

DevOps (Testing (Types (Unit Testing (Should be written by developers…

- - - - Selenium
      - Katalon
      - Watir
  - - - What is functional test
        
        https://en.wikipedia.org/wiki/Functional_testing
    - - Tools
        
        Test Libraries
        
        C#
        
        NUnit
        
        XUnit
        
        MsTest
        
        Saleforce DX
        
        JavaScript
        
        Mocka
        
        Jasmine
        
        Jest
        
        It was developed by Facebook developers
        
        Joins expect/asserts, stubs/mocks, and snapshots in one library
        
        Chai
        
        Useful assertion library, pairs well with Mocha
        
        Mock Libraries
        
        C#
        
        Moq
        
        MsTest
        
        Saleforce DX
        
        JavaScript
        
        Sinon.js
        
        Jasmine
      - Should be written by developers
        
        Examples should be provided by DevOps team
        
        Base classes, mock classes can be provided by DevOps team
        
        Old projects' unit test will be handled by DevOps team
      - Without unit test coverage, commiting the code must be blocked
      - What is unit test?
        
        https://en.wikipedia.org/wiki/Unit_testing
- - - - Takes time to configure
      - Tons of customization/addons
      - Support plugin development
      - maintaince of jenkins, dedicated server
      - Big community
      - Old style UI, basic dashboards
    - - doesn't support standard .net applications
      - easy to config / out of the box
      - good documentation
      - don't have enough customization and third party add-on
      - on the cloud
      - Fancy user interface, nice dashboards
    - - dotcover for testing and coverage app
      - IDE plugins (VS &Intelli)
      - Plugins / Customization
      - Small community compare to others
      - Fancy user interface, nice dashboards
    - - Can easily connect to our existing Github repositories
      - Largely platform-agnostic - should be able to integrate with Salesforce (dx/cli), Netsuite, Azure, etc.
      - Big community
      - Needs some initial setup for each platform we use; some might need additional tools for full integration
  - - - dev/test-uat/prod
      - build / deploy / all / partial update
    - - Before commit, changes must be compiled
      - If an error occurs, that will cancel commit/pull request
      - By this feature, errors won't be in branch commit history
      - Unit Test coverage must be checked before commit
        
        this tools can be integrated with GitHub
        
        can be warning in earlier stages
        
        there should be blocking commit
        
        Code coverage must be checked for only changed code
      - The error check is handled by CI tools which are integrated with VCS. But code coverage must be handled by another tool (integrated with CI and VCS)
    - - libra : dev (rackspace), prod (ireland,azure)
      - salesforce : both cloud, sandbox and salesforce prod, DX,CLI
      - netsuite : both cloud,sandbox and prod
        
        :warning: there is no known deployment tool for netsuite now
- - - - It can be integrated with github as zenhub or codetree
      - stand alone tools like Jira will be hard to manage
      - for kanban and github > zube or waffle
- - - - https://codecov.io/
      - integrated with CI
- - - - Delete script can be executed after production deployment
      - Every deployment should have branch id for tracking deployments
    - - Every development is implemented in Developer consoles of those applicaitons
      - Then developer copies changes to
  - - - Every Pull Request or change in main branches like Dev/Test, Master must be reviewed by developer manager and responsible people like project manager
      - Coding Standart must be written for all systems (salesfore,.net, netsuite)
      - Example of common library,service usage must be published
        
        Rhino, Buss usage
        
        Email, logging