How to disable checking of password, name, credit card info and any other fields for Locust load testing

[nyck33]

I want to use Saleor as a demo app for an OpenZiti + NVIDIA Morpheus demo so need to generate logs of normal traffic. Is there any way you can tell me which files to look in to make these adjustments so that I can programatically input random values for them in my Locust script? I just finished learning GraphQL and tried asking Cursor IDE with the entire code base of storefront as context but it's only giving me a partial answer.

[typeofweb]

I'm more than willing to assist, but I must admit that I'm not entirely certain about the specifics of what you're looking for. Could you please provide more details or clarify your question?

[nyck33]

That is because I was trying out your app, with the mock data loaded into Postgres (Saleor branded hoodies, beanies, shoes, etc), selected a few items and tried to check out but I actually needed a real credit card number, ie. could not input "1234 5678 9012 3456" as the validation would catch it. So in this instance, I would want validation to be disabled since when I run my Locust script, I am going to have a line in Python like

import random
credit_card_number = ''.join([str(random.randint(0, 9)) for _ in range(16)])

That lets me mock a user entering credit card info in the context of load testing the app.

I asked in the chat window of Cursor IDE the following with the entire code base as context:

"Look at the entire code base and tell me exactly what to refactor in which files so that the app wlll accept any value for: email used for registration, credit card info, first name, last name, password and any other fields you can think the app will ask for in order to regsiter and login. I want to be able to run Locust load test script on the app and want to just give these fields random values. "

Basically I want to bypass or turn off all validation of user input so my Locust script is free to focus on load testing rather than providing valid inputs which is impossible for something like credit card numbers since my Locust swarm will have 10,000 or so "users".

Cursor IDE chat window continued:

To make the application accept any value for the fields you mentioned, you would need to modify the validation rules for these fields in the application's code. Here are the files and the changes you would need to make:

1. Guest User Form Validation (useGuestUserForm.ts)

In the useGuestUserForm.ts file, the validation schema for the guest user form is defined. You would need to remove or modify the validation rules for the email, password, and createAccount fields.

	const validationSchema = object({
		createAccount: bool(),
		email: string().email(errorMessages.invalid).required(errorMessages.required),
		password: string().when(["createAccount"], ([createAccount], field) =>
			createAccount ? field.min(8, "Password must be at least 8 characters").required() : field,
		),
	}) as Schema<GuestUserFormData>;

2. Login Form Validation (LoginForm.tsx)

In the LoginForm.tsx file, the form values for the login form are defined and used. You would need to remove or modify the validation rules for the email and password fields.

	const [formValues, setFormValues] = useState<FormValues>(DefaultValues);
	const [errors, setErrors] = useState<string[]>([]);

	const submitHandler = async (event: FormEvent<HTMLFormElement>) => {
		event.preventDefault();

		const { data } = await signIn(formValues);

		if (data.tokenCreate.errors.length > 0) {
			setErrors(data.tokenCreate.errors.map((error) => error.message));
			setFormValues(DefaultValues);
		}
	};

	const changeHandler = (event: FormEvent<HTMLInputElement>) => {
		const { name, value } = event.currentTarget;
		setFormValues((prev) => ({ ...prev, [name]: value }));

		if (errors.length > 0) setErrors([]);
	};

	const [formValues, setFormValues] = useState<FormValues>(DefaultValues);
	const [errors, setErrors] = useState<string[]>([]);

	const submitHandler = async (event: FormEvent<HTMLFormElement>) => {
		event.preventDefault();

		const { data } = await signIn(formValues);

		if (data.tokenCreate.errors.length > 0) {
			setErrors(data.tokenCreate.errors.map((error) => error.message));
			setFormValues(DefaultValues);
		}
	};

	const changeHandler = (event: FormEvent<HTMLInputElement>) => {
		const { name, value } = event.currentTarget;
		setFormValues((prev) => ({ ...prev, [name]: value }));

		if (errors.length > 0) setErrors([]);
	};

3. Error Messages (useErrorMessages.ts and errorMessages.ts)

In the useErrorMessages.ts and errorMessages.ts files, the error messages for various validation errors are defined. You would need to modify these files to remove or change the error messages related to the fields you mentioned.

import { useCallback, useMemo } from "react";
import { type ErrorCode } from "@/checkout/lib/globalTypes";

export const errorMessages = {
	invalid: "Invalid value",
	required: "Required field",
	unique: "Value must be unique",
	emailInvalid: "Email must be a valid email",
	passwordAtLeastCharacters: "Password must be at least 8 characters",
	passwordTooShort: "Provided password is too short. Minimum length is 8 characters.",
	passwordTooSimilar: "Provided password is too similar to your previous password.",
	passwordTooCommon: "Provided password is too common. Use something more fancy.",
	passwordInvalid: "Provided password is invalid.",
	quantityGreaterThanLimit: "Chosen quantity is more than limit allowed.",
	insufficientStock: "Not enough of chosen item in stock.",
	invalidCredentials: "Invalid credentials provided at login.",
	missingFields: "Missing fields in address form: ",
} satisfies Record<ErrorCode, string>;

export type ErrorMessages = Record<ErrorCode, string>;

export const useErrorMessages = <TKey extends string = ErrorCode>(customMessages?: Record<TKey, string>) => {
	const messagesToUse = customMessages || errorMessages;

	const getMessageByErrorCode = useCallback(
		(errorCode: string) => {
			const formattedMessage = messagesToUse[errorCode as keyof typeof messagesToUse];
			if (!formattedMessage) {
				console.warn(`Missing trnalsation: ${errorCode}`);
				return "";
			}
			return formattedMessage;
		},
		[messagesToUse],
	);

	const translatedErrorMessages = useMemo(
		() =>
			Object.keys(messagesToUse).reduce(
				(result, key) => ({
					...result,
					[key]: getMessageByErrorCode(key as TKey),
				}),
				{} as Record<TKey, string>,
			),
		[getMessageByErrorCode, messagesToUse],
	);

	return {
		errorMessages: translatedErrorMessages,
		getMessageByErrorCode,
	};
};

export const apiErrorMessages = {
	somethingWentWrong: "Sorry, something went wrong. Please try again in a moment.",
	requestPasswordResetEmailNotFoundError: "User with provided email has not been found",
	requestPasswordResetEmailInactiveError: "User account with provided email is inactive",
	checkoutShippingUpdateCountryAreaRequiredError: "Please select country area for shipping address",
	checkoutBillingUpdateCountryAreaRequiredError: "Please select country area for billing address",
	checkoutFinalizePasswordRequiredError: "Please set user password before finalizing checkout",
	checkoutEmailUpdateEmailInvalidError: "Provided email is invalid",
	checkoutAddPromoCodePromoCodeInvalidError: "Invalid promo code provided",
	userAddressUpdatePostalCodeInvalidError: "Invalid postal code provided to address form",
	userAddressCreatePostalCodeInvalidError: "Invalid postal code provided to address form",
	userRegisterPasswordPasswordTooShortError: "Provided password is too short",
	checkoutPayShippingMethodNotSetError: "Please choose delivery method before finalizing checkout",
	checkoutEmailUpdateEmailRequiredError: "Email cannot be empty",
	checkoutPayTotalAmountMismatchError: "Couldn't finalize checkout, please try again",
	checkoutPayEmailNotSetError: "Please fill in email before finalizing checkout",
	userRegisterEmailUniqueError: "Cannot create account with email that is already used",
	loginEmailInactiveError: "Account with provided email is inactive",
	loginEmailNotFoundError: "Account with provided email was not found",
	loginEmailAccountNotConfirmedError: "Account hasn't been confirmed",
	resetPasswordPasswordPasswordTooShortError: "Provided password is too short",
	resetPasswordTokenInvalidError: "Provided reset password token is expired or invalid",
	checkoutLinesUpdateQuantityQuantityGreaterThanLimitError:
		"Couldn't update line - buy limit for this item exceeded",
	checkoutLinesUpdateQuantityInsufficientStockError: "Couldn't update line - insufficient stock in warehouse",
	signInEmailInvalidCredentialsError: "Invalid credentials provided to login",
	signInEmailInactiveError: "The account you're trying to sign in to is inactive",
	checkoutShippingUpdatePostalCodeInvalidError: "Invalid postal code was provided for shipping address",
	checkoutShippingUpdatePhoneInvalidError: "Invalid phone number was provided for shipping address",
	checkoutBillingUpdatePostalCodeInvalidError: "Invalid postal code was provided for billing address",
	checkoutDeliveryMethodUpdatePostalCodeInvalidError: "Invalid postal code was provided for shipping address",
	checkoutDeliveryMethodUpdatePromoCodeInvalidError: "Please provide a valid discount code.",
};

4. GraphQL Schema (schema.graphql)

In the schema.graphql file, the GraphQL schema for the application is defined. You would need to modify this file to remove or change the validation rules for the fields you mentioned.

"""
Groups fields and operations into named groups.
"""
directive @doc(
	"""
	Name of the grouping category
	"""
	category: String!
) on ENUM | FIELD | FIELD_DEFINITION | INPUT_OBJECT | OBJECT

"""
Webhook events triggered by a specific location.
"""
directive @webhookEventsInfo(
	"""
	List of asynchronous webhook events triggered by a specific location.
	"""
	asyncEvents: [WebhookEventTypeAsyncEnum!]!

	"""
	List of synchronous webhook events triggered by a specific location.
	"""
	syncEvents: [WebhookEventTypeSyncEnum!]!
) on FIELD | FIELD_DEFINITION | INPUT_OBJECT | OBJECT

"""
_Any value scalar as defined by Federation spec.
"""
scalar _Any

"""
_Entity union as defined by Federation spec.
"""
union _Entity =
	  App
	| Address
	| User
	| Group
	| ProductVariant
	| Product
	| ProductType
	| ProductMedia
	| Category
	| Collection
	| Order
	| PageType

"""
_Service manifest as defined by Federation spec.
"""
type _Service {
	sdl: String
}

"""
Create a new address for the customer.

Requires one of the following permissions: AUTHENTICATED_USER.

Triggers the following webhook events:
- CUSTOMER_UPDATED (async): A customer account was updated.
- ADDRESS_CREATED (async): An address was created.
"""
type AccountAddressCreate {
	"""
	A user instance for which the address was created.
	"""
	user: User
	accountErrors: [AccountError!]!
		@deprecated(reason: "This field will be removed in Saleor 4.0. Use [errors](file:///c%3A/Users/User/Documents/saleorStoreFront/src/checkout/sections/GuestUser/useGuestUserForm.ts#62%2C12-62%2C12) field instead.")
	errors: [AccountError!]!
	address: Address
}

"""
Delete an address of the logged-in user. Requires one of the following permissions: MANAGE_USERS, IS_OWNER.

Triggers the following webhook events:
- ADDRESS_DELETED (async): An address was deleted.
"""
type AccountAddressDelete {
	"""
	A user instance for which the address was deleted.
	"""
	user: User
	accountErrors: [AccountError!]!
		@deprecated(reason: "This field will be removed in Saleor 4.0. Use [errors](file:///c%3A/Users/User/Documents/saleorStoreFront/src/checkout/sections/GuestUser/useGuestUserForm.ts#62%2C12-62%2C12) field instead.")
	errors: [AccountError!]!
	address: Address
}

"""
Updates an address of the logged-in user. Requires one of the following permissions: MANAGE_USERS, IS_OWNER.

Triggers the following webhook events:
- ADDRESS_UPDATED (async): An address was updated.
"""
type AccountAddressUpdate {
	"""

Please note that these changes could have significant impacts on the application's functionality and security. It's generally not recommended to remove or weaken validation rules, especially for fields like email and password, as this could make the application vulnerable to various types of attacks.

Also, keep in mind that these changes would only affect the frontend validation. The backend server might also have its own validation rules for these fields, which you would need to modify separately.

[nyck33]

I'm not 100 percent sure as for the accuracy of the info given to me b ChatGPT in Cursor IDE but it's a starting point. It also suggests I would need to perform edits in saleor-platform since that is the backend? However, the code in that repo is a docker-compose.yml so I was going to try to docker cp the backend app out of the docker container, search the code base to see what needs editing and then make a new Docker container and image from that, ie. a version of the backend specifically for load testing.
If you have any vresions that you used during development for load testing, can you tell me where they are?

[nyck33]

I looked at Saleor Core and there is quite a bit of validatio logic in there, nested at times so can you advise on before I move forward tyring to disable it so I don't break it? I want the Docker container I'll make to work with Saleor Platform so version 3.17 is what I am looking to edit. @mmiszy At some point, you must have load tested it and had a version that would accept dummy data.

[typeofweb]

So you just want to disable address validation?

[nyck33]

@mmiszy if possible, all of it so Locust can just run wild :)

[typeofweb]

But what would be the point of that?
Providing an invalid address makes it impossible to fetch and select a shipping method.
Some products may be limited to certain shipping locations.
And load testing with validation disabled will likely give you inaccurate results.

[nyck33]

What do you suggest? Can I use the same address for my entire Locust swarm?
Just going through each step, I still think is okay for log creation. Then someone deploying the Saleor stack can have Morpheus running from day one rather than having to wait until there is sufficient log to train ML models on.
Credit card number, I noticed that fake numbers will not work so if anything can you walk me through disabling it?