u/pc/rhodecode-enterprise-ce-fork-pc Files · docs/contributing/testing/index.rst

auth: don't break hashing in case of user with empty password....

auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.

lisaq - - Load All Authors

File last commit:

r271:401985cc default


                r2203:8a18c3c3

default

Download file

             index.rst
        
                    28 lines
            
             | 694 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / contributing / testing / index.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      ============================

       Testing and Specifications

      ============================

      .. toctree::

         :maxdepth: 2

         unit-and-functional

         spec-by-example

         naming-conventions

      Overview

      ========

        lisaq
    
docs: updates to contributor documentation #4039

              r271
            
      We have a quite large test suite inside of :file:`rhodecode/tests` which is a mix

        marcink
    
project: added all source files and assets

              r1
            
      of unit tests and functional or integration tests. More details are in

      :ref:`test-unit-and-functional`.

        lisaq
    
docs: updates to contributor documentation #4039

              r271
            
      Apart from that, we are starting to apply "Specification by Example" and maintain

      a collection of such specifications together with an implementation so that it

      can be validated in an automatic way. The files can be found in

        marcink
    
project: added all source files and assets

              r1
            
      :file:`acceptance_tests`. More details are in :ref:`test-spec-by-example`.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

marcink project: added all source files and assets	r1

		============================
		Testing and Specifications
		============================


		.. toctree::
		:maxdepth: 2

		unit-and-functional
		spec-by-example
		naming-conventions



		Overview
		========

lisaq docs: updates to contributor documentation #4039	r271	We have a quite large test suite inside of :file:`rhodecode/tests` which is a mix
marcink project: added all source files and assets	r1	of unit tests and functional or integration tests. More details are in
		:ref:`test-unit-and-functional`.


lisaq docs: updates to contributor documentation #4039	r271	Apart from that, we are starting to apply "Specification by Example" and maintain
		a collection of such specifications together with an implementation so that it
		can be validated in an automatic way. The files can be found in
marcink project: added all source files and assets	r1	:file:`acceptance_tests`. More details are in :ref:`test-spec-by-example`.