Develop Branch to Master Branch #13
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To create unit tests for the app.py script using pytest, we need to focus on testing different functionalities like the session states, file upload, PDF loading, text splitting, vector store creation, and the QA chain. Since the script uses external libraries like LangChain and Streamlit, we'll mock the dependencies for proper testing.
GitHub Actions YAML workflow that runs the pytest tests for the app.py application and the test_app.py script. This YAML file will automate the testing process each time a commit is pushed or a pull request is created.
Modify the GitHub Actions workflow to: - Install dependencies from a requirements.txt file. - Run the workflow only on the develop branch (instead of main).
This should fix the pytest: command not found error by ensuring that pytest is properly installed and executed in the correct environment.
Key Fixes: setup_streamlit_session_state: The autouse=True fixture initializes the Streamlit session state for each test. This is crucial to avoid the AttributeError for missing session state variables like template, prompt, vectorstore, etc. Mock objects: Since the vectorstore, llm, and other session state variables are complex objects, they are mocked to avoid needing to initialize them with actual functionality during the tests. This allows the tests to focus on the logic and session state, not the external dependencies.
Explanation of Fixes in test_app.py: Session State Initialization: The session state is initialized in the test setup, so tests that depend on it (test_initial_session_state, test_chat_interaction, etc.) don't throw AttributeError. Mocks: Dependencies like llm, vectorstore, and qa_chain are mocked to avoid actual interactions with LangChain or external libraries. This keeps the tests fast and isolated. With these changes, the tests should now pass without session state or attribute errors.
o ensure the GitHub Actions workflow continues running even if some of the test cases fail, you can modify the workflow to add the continue-on-error flag to the job that runs the tests. This way, the test suite will run to completion, and the workflow will not stop immediately when a test fails. Here’s the updated .github/workflows/python-app.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create unit tests for the app.py script using pytest, we need to focus on testing different functionalities like the session states, file upload, PDF loading, text splitting, vector store creation, and the QA chain. Since the script uses external libraries like LangChain and Streamlit, we'll mock the dependencies for proper testing.