Please enable JavaScript.
Coggle requires JavaScript to display documents.
Alberts Solar Calculator's Test Strategy - Coggle Diagram
Alberts Solar Calculator's Test Strategy
Scope
With in the Scope
Functional Testing
Outputs from the calcilator
Life Sum of Net Present Value Grid Cost ($)
Life Sum of Net Present Value PV Cost
Levelized Cost of Energy (LCOE) ($/kWh) ?
Payback (yrs) ?
Levelized Avoided Cost of Energy (LACE) ($/kWh) ?
LACE-LCOE ($/kWh) ?
Discounted Return on Investment (ROI) (% after project life) ?
Discounted Return on Investment (ROI) (%) (Annual) ?
Inputs to the calculator
Grid Electricity Costs
variable costs
Transmission
Distribution
Energy
Type of Service
Residential
Commercial
Basic Electricity Cost ($/kWh)
PV Output
The capacity of the system (DCkW)
Estimation for annual PV energy
Site Usage
Monthly Estimation
Percent of Solar PV Generation
Project Costs
Total Project Cost
Rebate per installed Watt
Maximum Rebate Percentage
Maximum Rebate ($)
Financial Analysis Period (years)
If using loan
Downpayment ($)
Term (Years)
Annual Interest (%)
Annual Insurance Cost Estimate ($/year)
Annual General Maintenance Budget Amount ($/year)
Scheduled replacement/upgrade or overhaul Cost ($)
Years between scheduled replacement/overhaul (years)
Inflation and Cost
Escalators
General Inflation (%/year)
Electricity Rate Escalator (%/year)
T&D Rate Escalator ($/kWh/year)
Maintenance Cost Escalator (%/year)
Bank of Canada Prime Rate (%)
PV Investment Risk Premium (%)
Sales Tax (GST or HST) (%)
Economic Indicators
Non Functional Testing
Performance Testing
Less than 2500 users
2500 users
more than 2500 users
Compatibility
devices
desktop
ipads
Mobiles
iphone
Android
laptops
Web browsers
firefox
Chrome
Microsoft Edge
Safari
Outside the Scope
Security Testing
No bruteforce attack
No personal information shared
Compatibility
Operating System
Windows 8/10/11
Apple
Test Environment
Activities
Prepare a list of software required for the testing process
Prepare a list of hardware required for the testing process.
Setup test environment.
execute smoke test
Stage Test environment
Pre-Production environment
QA Test environment
Production environment
Testing Tools
Performance Testing
Jmeter
Security Testing
BurpSuite
Web UI
Selenium Webdriver
Bug Management
Trello , MentisBT
Roles & Responsibilities
Test lead
Planning and organization of test process for the release
Define project directions and implement
Acquire appropriate resources for the project
Coordinate with QA analysts/engineers on any
issues/problems encountered during testing
Tester
Identify the project requirements
Write Test cases and do peer review
Identifying and describing appropriate test techniques/tools/automation architecture
Verify and assess the Test Approach
Execute the tests, Log results, Report the defects.
Preparing RTM.
Bug review meeting
Developer
Work with system admin to do the deployment tasks in various environments
Development bug fix activity
System Admin
Release deployment to various environments
Setup and maintaining test environments with up-to-date information
Project Manager
Scheduling
Provide technical direction
Release Cretiera
According to requirements
According to Defects
According to test coverage
According to deadline
According to Compatibility
Release Control
Unit tests Completed before integration
Integration Testing completed before system Testing
Check for previous versions
pass acceptance testing
Test Strategy
Test Management
test cases, test results are updated in MentisBt
Read/Write Access will be provided for the corresponding users
Any defect encountered will be raised in the mantis bug tracker linking to the particular
test case/test step.
Reports generation
Test Design
Each Test cases will be mapped with traceability matrix
Maintain Track sheet
Review by Business Analyst
Test Execution
Test cases approved
Test Environment Set up done
Exploratory Testing
If any failures, defects will be raised
Status of daily test execution as well as defect status will be reported to all stakeholders.
Risk and Mitigation
Undefined Project scope
testing schedule is tight.
Early communication with involved parties
Add buffer to the schedule
Not enough resources
Plan ahead
Make use of holidays
Defects are found at a later stage of the cycle
ensure prompt communication
Scope completely undefined
Define the scope adopting on going changes
Natural Disaster
Have backup sever
Teams are separated
Freshers included in the project
provide Training
Lack of Technical Knowledge
provide more technical training
Arrange KT sessions
Review and Approval
Track changes
Sign Off by project manager
Sign Off by product Owner
Prepare Test Summary