starred/proxyman-windows-linux
1
0
Fork 0
mirror of https://github.com/ProxymanApp/proxyman-windows-linux.git synced 2026-04-27 08:55:50 +03:00
Code Issues 541 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #133] Write Unit Tests #135

New issue
Open
opened 2026-03-03 19:48:49 +03:00 by kerem · 2 comments
kerem commented 2026-03-03 19:48:49 +03:00
Owner
Copy link

Originally created by @NghiaTranUIT on GitHub (Nov 7, 2022).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/133

Originally assigned to: @kics223w1 on GitHub.

Description

Let double check some important use cases and write some missing unit tests

Acceptance Criteria

All current Unit Tests should be passed

  • filter.test.jsx
  • harBuilder.jsx
  • harmodel.jsx
  • sslproxying.test.jsx
  • proxycore.js

Add new unit tests

proxymanlogv2.test.jsx

  • Export to proxymanlogv2 -> Import again -> Check they are the same
  • Import a proxymanlogv2 file (export from Proxyman for macOS) -> Import to app -> Test if they are the same (Same number of flow, same request/response)

proxycore.test.js

The general idea of how to write unit tests for the ProxyCore.

  1. Start the proxyServer at port 10000 (Must Disable all Tools)
  2. Make a Request to http://httpbin.org by Axios (Axios must proxy to localhost:10000)
  3. Get the response from Axios
  4. Verify the Response with the expected output
  • Make a GET HTTP (http://httpbin.org) with some query -> Verify the Response
  • Make sure to Enable SSL proxying on the httpbin.org -> Make a POST HTTPS (https://httpbin.org) with some query, JSON Body -> Verify the Response
  • Make sure to Enable SSL proxying on the httpbin.org -> Make a POST HTTPS (https://httpbin.org) with some query, Form Body -> Verify the Response

repeat-tool.test.js

  1. Start the proxyServer at port 10000 (Must Disable all Tools)
  2. Make a Request to http://httpbin.org by Axios (Axios must proxy to localhost:10000)
  3. Get the flow from the Flow Pool -> Repeat this flow
  4. Verify the Response with the expected output
  • Make a GET HTTP (http://httpbin.org) with some query
  • Make sure to Enable SSL proxying on the httpbin.org -> Make a POST HTTPS (https://httpbin.org) with some query, JSON Body -> Verify the Response
  • Make sure to Enable SSL proxying on the httpbin.org -> Make a POST HTTPS (https://httpbin.org) with some query, Form Body -> Verify the Response

no-caching-tool.test.js

  1. Start the proxyServer at port 10000 (Must Disable all Tools)
  2. Enable the No Caching Tool
  3. Make a Request to http://httpbin.org by Axios (Axios must proxy to localhost:10000)
  4. Get the response from Axios
  5. Verify the Response with the expected output
  • Make a GET HTTPS (https://httpbin.org) with some query -> Verify the Response header has some no-caching header
Originally created by @NghiaTranUIT on GitHub (Nov 7, 2022). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/133 Originally assigned to: @kics223w1 on GitHub. ## Description Let double check some important use cases and write some missing unit tests ## Acceptance Criteria ### All current Unit Tests should be passed - [x] `filter.test.jsx` - [x] `harBuilder.jsx` - [x] `harmodel.jsx` - [x] `sslproxying.test.jsx` - [x] `proxycore.js` ### Add new unit tests #### proxymanlogv2.test.jsx - [x] Export to proxymanlogv2 -> Import again -> Check they are the same - [ ] Import a `proxymanlogv2` file (export from Proxyman for macOS) -> Import to app -> Test if they are the same (Same number of flow, same request/response) #### proxycore.test.js The general idea of how to write unit tests for the ProxyCore. 1. Start the proxyServer at port 10000 (Must Disable all Tools) 2. Make a Request to http://httpbin.org by Axios (Axios must proxy to localhost:10000) 3. Get the response from Axios 4. Verify the Response with the expected output - [x] Make a GET HTTP (http://httpbin.org) with some query -> Verify the Response - [x] Make sure to Enable SSL proxying on the `httpbin.org` -> Make a POST HTTPS (https://httpbin.org) with some query, JSON Body -> Verify the Response - [x] Make sure to Enable SSL proxying on the `httpbin.org` -> Make a POST HTTPS (https://httpbin.org) with some query, Form Body -> Verify the Response #### repeat-tool.test.js 1. Start the proxyServer at port 10000 (Must Disable all Tools) 2. Make a Request to http://httpbin.org by Axios (Axios must proxy to localhost:10000) 3. Get the flow from the Flow Pool -> Repeat this flow 4. Verify the Response with the expected output - [x] Make a GET HTTP (http://httpbin.org) with some query - [x] Make sure to Enable SSL proxying on the `httpbin.org` -> Make a POST HTTPS (https://httpbin.org) with some query, JSON Body -> Verify the Response - [x] Make sure to Enable SSL proxying on the `httpbin.org` -> Make a POST HTTPS (https://httpbin.org) with some query, Form Body -> Verify the Response #### no-caching-tool.test.js 1. Start the proxyServer at port 10000 (Must Disable all Tools) 2. Enable the No Caching Tool 3. Make a Request to http://httpbin.org by Axios (Axios must proxy to localhost:10000) 4. Get the response from Axios 5. Verify the Response with the expected output - [x] Make a GET HTTPS (https://httpbin.org) with some query -> Verify the Response header has some no-caching header
kerem commented 2026-03-03 19:48:50 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Nov 14, 2022):

Requirement Update 1

  • Make sure to Enable SSL proxying on the httpbin.org -> Make a GET HTTPS (https://httpbin.org/get) with some query by axios -> Verify the axios successes and response body has correct data.
<!-- gh-comment-id:1313331747 --> @NghiaTranUIT commented on GitHub (Nov 14, 2022): ### Requirement Update 1 - [x] Make sure to Enable SSL proxying on the httpbin.org -> Make a GET HTTPS (https://httpbin.org/get) with some query by axios -> Verify the axios successes and response body has correct data.
kerem commented 2026-03-03 19:48:50 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Nov 16, 2022):

Requirement Update 2

  • Try to run the Unit Tests on Ubuntu VM instance (instead of macOS, because it's 3x expense)
  • Combine npm run jest + npm run test into 1 Job
<!-- gh-comment-id:1316182283 --> @NghiaTranUIT commented on GitHub (Nov 16, 2022): ## Requirement Update 2 - [ ] Try to run the Unit Tests on Ubuntu VM instance (instead of macOS, because it's 3x expense) - [x] Combine `npm run jest` + `npm run test` into 1 Job
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/new-version
3.12.0
3.11.0
3.10.0
3.4.0
3.5.0
3.6.0
3.7.0
3.8.0
3.9.0
3.3.0
2.25.0
2.24.0
3.2.0
3.0.0
3.1.0
2.26.0
2.27.0
2.23.0
2.22.0
2.21.0
2.20.0
2.19.0
2.18.0
2.17.0
2.16.0
2.15.0
2.14.0
2.13.0
2.12.0
2.11.1
2.11.0
2.10.0
2.9.0
2.8.0
2.7.0
2.6.0
2.5.0
2.4.0
2.3.0
1.9.2
2.0.0
1.9.1
1.8.1
1.9.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.10.0
0.9.0
0.8.0
0.6.0
0.5.0
0.4.2
0.4.1
0.4.0
0.3.0
0.1.1
0.2.0
0.1.0
Labels
Clear labels   
Linux

   
bug

   
enhancement

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
✅ Done
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxyman-windows-linux#135
No description provided.