How goutham3991/isbnetbanking works
ISBNetBanking is a Playwright end-to-end automation framework, not the banking application itself. Its main workflow is to run banking test suites through shared fixtures and page objects against the application, then produce test reports. The graph also captures documented authentication and AI-assisted scenario capabilities. Relationship evidence is limited to the README and the sampled configuration and page-object files; test and fixture implementations were not sampled.
Main entry points: tests Test suites · loginPage.js Login page · playwright.config.js Playwright runner · auth.setup.js Authentication setup
Components 28
Banking test suites
- Test suites
tests - Login tests
tests/login - Account tests
tests/accounts - Transfer tests
tests/fund transfer - Bill payment tests
tests/bill payments - Fixed deposit tests
tests/fixed deposit - Loan tests
tests/loan calculator - Notification tests
tests/notifications - Transaction tests
tests/transactions
Page objects
- Login page
pages/loginPage.js - Dashboard page
pages/dashboardPage.js - Account page
pages/accountPage.js - Transfer page
pages/transfers.js - Bill payments page
pages/payBillsPage.js - Fixed deposit page
pages/fixedDepositPage.js - Loan calculator page
pages/loanCalculatorPage.js - Notifications page
pages/notificationPage.js - Transactions page
pages/transactionsPage.js
Execution runtime
- Reusable fixtures
fixtures - Playwright runner
playwright.config.js - Chromium browser
playwright.config.js - Test reports
playwright.config.js
Test support
- Authentication setup
tests/auth.setup.js - Storage-state auth
playwright.config.js - AI test scenarios
ai/ai-generated-test-scenarios - Playwright MCP
.playwright-mcp
Other components
- Test engineer
- Banking application
Connections 31
- Test engineer → Test suites: selects tests
README.md - Test suites → Playwright runner: runs in
README.md - Test suites → Reusable fixtures: uses fixtures
README.md - Reusable fixtures → Login page: provides page objects
- Test suites → Login page: uses page objects
README.md - Test suites → Banking application: automates
README.md - Playwright runner → Chromium browser: configures
playwright.config.js - Chromium browser → Banking application: drives browser
- Login tests → Login page: uses
- Account tests → Account page: uses
- Transfer tests → Transfer page: uses
- Bill payment tests → Bill payments page: uses
- Fixed deposit tests → Fixed deposit page: uses
- Loan tests → Loan calculator page: uses
- Notification tests → Notifications page: uses
- Transaction tests → Transactions page: uses
- Authentication setup → Login page: performs login
- Authentication setup → Storage-state auth: saves state
- Playwright runner → Storage-state auth: loads state
playwright.config.js - Playwright runner → Test reports: produces reports
playwright.config.js - Test engineer → AI test scenarios: reviews scenarios
README.md - Playwright MCP → AI test scenarios: supports exploration
- Dashboard page → Banking application: interacts with
pages/dashboardPage.js - Login page → Banking application: interacts with
pages/loginPage.js - Account page → Banking application: interacts with
pages/accountPage.js - Transfer page → Banking application: interacts with
pages/transfers.js - Bill payments page → Banking application: interacts with
pages/payBillsPage.js - Fixed deposit page → Banking application: interacts with
pages/fixedDepositPage.js - Loan calculator page → Banking application: interacts with
pages/loanCalculatorPage.js - Notifications page → Banking application: interacts with
pages/notificationPage.js - Transactions page → Banking application: interacts with
pages/transactionsPage.js