[GITEA] Enable mocked HTTP responses for GitLab migration test
Fix gitlab migration unit test Closes #1837. The differences in dates can be explained by commite19b9653ea, which changed the order in which "created_date" and "updated_date" are considered. (cherry picked from commitb0bba20aa4) Mock HTTP requests in GitLab migration test This introduces a new utility which can be added to other tests making HTTP calls to a live service, to cache the responses of this service in the repository. (cherry picked from commit52053b1389) Enable mocked HTTP responses for GitLab migration test (cherry picked from commit19cefc4de2) Simplify HTTP mocking utility in unit tests Follow-up to https://codeberg.org/forgejo/forgejo/pulls/1841 (cherry picked from commitca517c8bb4) (cherry picked from commitb227e0dd6b) (cherry picked from commit6cc9d06556) (cherry picked from commitf0746e648d) (cherry picked from commit414193341b) (cherry picked from commit6e93df3bbb) (cherry picked from commitdb0dbab552) (cherry picked from commit8f9c9c63fb) (cherry picked from commite74e262030) (cherry picked from commit2e0933edcf) (cherry picked from commit65060c6961)
This commit is contained in:
		
							parent
							
								
									21c4d844f3
								
							
						
					
					
						commit
						01b0ead664
					
				
					 24 changed files with 708 additions and 22 deletions
				
			
		| 
						 | 
				
			
			@ -100,6 +100,8 @@ package "code.gitea.io/gitea/models/unittest"
 | 
			
		|||
	func LoadFixtures
 | 
			
		||||
	func Copy
 | 
			
		||||
	func CopyDir
 | 
			
		||||
	func NewMockWebServer
 | 
			
		||||
	func NormalizedFullPath
 | 
			
		||||
	func FixturesDir
 | 
			
		||||
	func fatalTestError
 | 
			
		||||
	func InitSettings
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue